canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
Jump to navigation
Jump to search
→Guiding Principles
| Line 4: | Line 4: | ||
Mozilla aims to advance the state of the open Web with new APIs. In the last few years, Mozilla has shipped experimental APIs with a "moz" prefix to indicate their lack of standardization (e.g., mozRequestAnimationFrame()). Unfortunately, this approach turned out to be harmful to the Web as experimental APIs ended up being used in some websites before the APIs were ready. In many cases, this meant that we were unable to innovate on certain APIs because to change them would break content on the Web. Therefore, to allow us to continue innovating without negatively affecting content on the Web, '''Mozilla will no longer ship new "moz"-prefixed APIs''' (see [https://groups.google.com/forum/#!topic/mozilla.dev.platform/34JfwyEh5e4 Henri Sivonen's proposal]). | Mozilla aims to advance the state of the open Web with new APIs. In the last few years, Mozilla has shipped experimental APIs with a "moz" prefix to indicate their lack of standardization (e.g., mozRequestAnimationFrame()). Unfortunately, this approach turned out to be harmful to the Web as experimental APIs ended up being used in some websites before the APIs were ready. In many cases, this meant that we were unable to innovate on certain APIs because to change them would break content on the Web. Therefore, to allow us to continue innovating without negatively affecting content on the Web, '''Mozilla will no longer ship new "moz"-prefixed APIs''' (see [https://groups.google.com/forum/#!topic/mozilla.dev.platform/34JfwyEh5e4 Henri Sivonen's proposal]). | ||
We will instead make experimental APIs available behind preferences which can be toggled through <tt>about:config</tt>. Once we | We will instead make experimental APIs available behind preferences which can be toggled through <tt>about:config</tt>. Once we feel there is an acceptable level of consensus in the Web community about the stability of an API and we feel it is ready, we will make it generally available to the platform (more details below on this process). We feel this strikes the right balance between allowing developers to experiment with new APIs, while at the same time protecting the Web from being exposed to new functionality prematurely. | ||
==Special Cases== | ==Special Cases== | ||