Primary eng/PM emails
Spec
Summary
Adds canvas.supportsContext() to allow developers to query supported context types without needing to create them.
Motivation
Toolkits such as Modernizr want to report canvas capabilities in a non-obtrusive way. Currently they must either create a context, which has a lot of overhead, or they must estimate support by testing for the existence of types, such as "if (window.WebGLRenderingContext) { ... }". This may give false positives if the browser supports WebGL but has it disabled.
Compatibility Risk
Very low. A single new function will be added and existing APIs will not be changed.
Ongoing technical constraints
None.
Will this feature be supported on all five Blink platforms (Windows, Mac, Linux, Chrome OS and Android)?
Yes.
OWP launch tracking bug?
No launch bug, but a feature request bug exists: https://code.google.com/p/chromium/issues/detail?id=251027
Row on feature dashboard?
No. This is a small change which can reasonably be encompassed by "Canvas"
Requesting approval to ship?
Yes.
Primary eng/PM emails
Spec
Summary
Adds canvas.supportsContext() to allow developers to query supported context types without needing to create them.
Motivation
Toolkits such as Modernizr want to report canvas capabilities in a non-obtrusive way. Currently they must either create a context, which has a lot of overhead, or they must estimate support by testing for the existence of types, such as "if (window.WebGLRenderingContext) { ... }". This may give false positives if the browser supports WebGL but has it disabled.
Compatibility Risk
Very low. A single new function will be added and existing APIs will not be changed.
Motivation
Toolkits such as Modernizr want to report canvas capabilities in a non-obtrusive way. Currently they must either create a context, which has a lot of overhead, or they must estimate support by testing for the existence of types, such as "if (window.WebGLRenderingContext) { ... }". This may give false positives if the browser supports WebGL but has it disabled.
This part of the template isn't just the notion of size of the change (we refer to it as "footprint"), but also how likely it is that other browsers will also implement it, whether or not a spec exists, etc. It looks like this is in the WHATWG HTML spec already based on the link above. Do other browsers support it or plan to support it?