117095 2013-05-31 14:43:55 -0700 HTMLCanvasElement getContext and supportsContext functions assumes that a canvas cannot be changed after creation 2013-06-14 10:37:14 -0700 1 1 1 Unclassified WebKit Canvas 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID InRadar P2 Normal --- 0 ruthiecftg webkit-unassigned dino ian ruthiecftg webkit-bug-importer oldest_to_newest 895998 0 ruthiecftg 2013-05-31 14:43:55 -0700 The implementations of getContext and supportsContext (once the patch for bug 70117 is landed) in Source/WebCore/html/HTMLCanvasElement.cpp depends on the assumption that the context does not go away upon creation (to prevent JS form seeing a dangling pointer) and disallows the context from being changed once it is created. Thus, if a 3d context exists for a <canvas> element (by calling canvas.getsContext('webkit-3d') and supportsContext('2d') is subsequently called on that <canvas> element, then canvas.supportsContext('2d') will return false because a 3d context already exists. 895999 1 webkit-bug-importer 2013-05-31 14:44:14 -0700 <rdar://problem/14037988> 900593 2 ian 2013-06-14 10:00:50 -0700 Why is that a bug? Isn't that exactly what the spec requires? 900603 3 ruthiecftg 2013-06-14 10:34:53 -0700 (In reply to comment #2) > Why is that a bug? Isn't that exactly what the spec requires? Just checked with Dean; you're right. 900604 4 dino 2013-06-14 10:37:14 -0700 I believe it was me who gave this erroneous suggestion.