2012/12/5 Henri Sivonen <hsivo...@iki.fi> > Therefore, I propose that we adopt the following policy: > 1) Excluding WebGL and WebRTC APIs, new APIs that are shipped on the > release channel shall be shipped without a prefix. > 2) If APIs that don’t already have specs are shipped, we’ll get specs > written. > > (For clarity, the above formulation does not require WebGL or WebRTC > to have prefixes.) >
Thanks. To be clear and to conclude this on a positive note, the context of our WG commitment in the case of WebGL is that WebGL prefixes are reasonably kept under control: - Only WebGL extensions can have suffixes, not core WebGL functionality; - The WebGL API is designed so that you can't accidentally rely on an extension (you have to explicitly call getExtension before you can use any non-core functionality). - There is a definite process to drop WebGL extension suffixes, so we can drop suffixes on WebGL extensions that reach "community approved" status, which actually happens in practice, typically after a few months or real-world testing. A couple draft WebGL extensions are overdue now for promoting to community status, but other than that, the process is not too bad. Benoit > > -- > Henri Sivonen > hsivo...@iki.fi > http://hsivonen.iki.fi/ > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
