That is an interesting idea. I think I’m in favor too. I don’t think it has been discussed at all. Since applications will have to be changed to request a WebGL 2 context instead of a WebGL 1 context, strict compatibility is not essential. I agree we should have a discussion about a process for getting rid of cruft.
Yes. One solution is to make any shared extension document interactions with both WebGL 1 and WebGL 2 in the same way the native OES_texture_float_linear does for ES 2 and ES 3.
Description: Message signed with OpenPGP using GPGMail