ExposureGuidelines: Difference between revisions

There will of course be special cases where we deviate from this goal.  New user-facing products like Firefox OS may need to ship APIs that have not yet been embraced by other browser engines or thoroughly discussed by standards bodies.  This allows Mozilla to provide functionality that other browser engines aren't working on or the majority of the Web community isn't interested in at that time.  Examples of such functionality include telephony and Bluetooth.  This functionality is most often only exposed to Firefox OS applications of elevated privileges and not via the Firefox OS browser application.  Developing these features without much involvement from the Web community comes with the price of temporary proprietary APIs.  Products such as Firefox OS ship these APIs as a part of their product but not to the broader web when they are not ready for such exposure.  This clearly indicates their lack of standardization at that time and limits the number of developers relying upon them.  Mozilla will learn from efforts such as Firefox OS and use this knowledge to inform various standardization efforts.  Our aim is to standardize our proprietary APIs as soon as possible so they become available on a royalty-free basis for the benefit of the Web community at large.