Closed Bug 1187174 Opened 4 years ago Closed 4 years ago

Use "webgl2" not "experimental-webgl2"

Categories

(Core :: Canvas: WebGL, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox42 --- fixed

People

(Reporter: jgilbert, Assigned: jgilbert)

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

We've talked in the WebGL WG, and we think there's no longer a compelling reason to have an "experimental-webgl2" phase:
* We can release previews hidden behind flags.
* We can't release something unsafe to the general web anyway.
* If webgl2 is safe, we can just call it "webgl2".
Attachment #8638277 - Flags: review?(dglastonbury)
Comment on attachment 8638277 [details] [diff] [review]
0001-Use-webgl2-not-experimental-webgl2.patch

Review of attachment 8638277 [details] [diff] [review]:
-----------------------------------------------------------------

I hope that Khronos test get updated to ask for webgl2 then...
Attachment #8638277 - Flags: review?(dglastonbury) → review+
(In reply to Dan Glastonbury :djg :kamidphish from comment #1)
> Comment on attachment 8638277 [details] [diff] [review]
> 0001-Use-webgl2-not-experimental-webgl2.patch
> 
> Review of attachment 8638277 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> I hope that Khronos test get updated to ask for webgl2 then...

It asks for 'webgl2', then 'experimental-webgl2'.
https://hg.mozilla.org/mozilla-central/rev/d1f3d202a195
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
I thought "experimental-" was "We have an implementation, it hasn't passed the conformance suite yet", not a commentary on its safety... basically a way to get not-100%-conformant implementations out there so that people can tinker without fiddling with flags?
(In reply to Vladimir Vukicevic [:vlad] [:vladv] from comment #5)
> I thought "experimental-" was "We have an implementation, it hasn't passed
> the conformance suite yet", not a commentary on its safety... basically a
> way to get not-100%-conformant implementations out there so that people can
> tinker without fiddling with flags?

Non-experimental already doesn't mean much. It only means that some previous version of the product has passed some previous version of the conformance tests. If we want a way to query how conformance an implementation can be claimed to be, we really need an API for it that's more specific than the current experimental/non-experimental division.

We will likely expose 'webgl2' contexts before we can claim webgl2 conformance.
You need to log in before you can comment on or make changes to this bug.