Open
Bug 878155
Opened 11 years ago
Updated 2 years ago
Remove or make a standard out of canvas@moz-opaque
Categories
(Core :: Graphics: Canvas2D, task)
Core
Graphics: Canvas2D
Tracking
()
NEW
People
(Reporter: bruant.d, Unassigned)
References
(Blocks 3 open bugs)
Details
(Keywords: site-compat)
It's been added ~5 years ago [1], has not been really documented besides 2 lines [2] so it's unlikely to be use widely if at all on the web. It's been promoted in a recent hacks article [3] (which I'm not sure is a good thing, but that's a different topic). If this feature is legit and holds its high-performance promise, it should be brought to standardization (or at least it should be attempted). If, for whatever reason, current state-of-the-art <canvas> implementations don't need this attribute to achieve high-performance, it should probably be removed (at least from content) Opinions? [1] https://bugzilla.mozilla.org/show_bug.cgi?id=430906 [2] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/3.5#New_Canvas_features [3] https://hacks.mozilla.org/2013/05/optimizing-your-javascript-game-for-firefox-os/
Comment 2•11 years ago
|
||
Three.js apparently at least considered using this; not sure whether they did. In any case, there is quite a bit of standardization discussion in this area. For example, see http://wiki.whatwg.org/wiki/CanvasOpaque and the discussion in the thread that contains http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Mar/0109.html just from a quick search.
Component: DOM: Core & HTML → Canvas: 2D
Reporter | ||
Updated•6 years ago
|
Blocks: proprietary-dom
Updated•5 years ago
|
Keywords: site-compat
Updated•5 years ago
|
Type: defect → task
Updated•4 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•