Remove or make a standard out of canvas@moz-opaque

RESOLVED INACTIVE

Status

()

Core
Canvas: 2D
RESOLVED INACTIVE
5 years ago
3 days ago

People

(Reporter: David Bruant, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
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/
We should probably drop this.
OS: Linux → All
Hardware: x86 → All
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

Comment 3

3 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 3 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.