1187174 - Use "webgl2" not "experimental-webgl2"

Status: RESOLVED FIXED

(Core :: Graphics: CanvasWebGL, defect)

Description

[Kelsey Gilbert [:jgilbert]]

Attachment: 0001-Use-webgl2-not-experimental-webgl2.patch

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".

Comment 1

[u480271]

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...

Comment 2

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/d1f3d202a195

Comment 3

[Kelsey Gilbert [:jgilbert]]

(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'.

Comment 4

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/d1f3d202a195

Comment 5

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

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?

Comment 6

[Kelsey Gilbert [:jgilbert]]

(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.

Comment 7

[Florian Scholz (Open Web Docs)]

https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/getContext#Browser_compatibility