Let's get it enabled on mozilla-central and ship this puppy.
Assignee: nobody → vladimir
Should this be turned into a meta-bug where we collect bugs that are serious enough to prevent us from enabling WebGL by default?
If we're going to do this for FF4, it needs to hit beta5 feature freeze. Marking that as the current plan, although I don't see how we actually have the resources to do this and I think we should cut it.
blocking2.0: --- → beta5+
Why should be cut it? Vlad and myself are working on it.
Depends on: 582053
Assignee: vladimir → nobody
Component: Graphics → Canvas: WebGL
QA Contact: thebes → canvas.webgl
A little status update. As far as I know, there are 2 major blockers here: 1) WebGL must be covered by a mochitest. Fortunately, bug 582053 does exactly that. I just attached a hopefully final version of my patch, so, hopefully this will be checked in soon. 2) Security-wise, we need a driver blacklist. However I don't think that this issue should be blocking beta5, only final. So, I guess that we should do things in this order: - get bug 582053 checked in - enable WebGL by default - implement the driver blacklising (not necessarily before beta5). Is this OK?
Great, bug 584536 is already taking care of the driver blacklist/whitelist, and is already tagged as blocking this one.
This was marked as blocking beta5. Now that the feature freeze is shifted to sep. 10, I guess this is our new target.
blocking2.0: beta5+ → ?
blocking2.0: ? → beta6+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 596720
You need to log in before you can comment on or make changes to this bug.