ExposureGuidelines: Difference between revisions

There may be special cases where we deviate from this goal. New user-facing 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. We will avoid exposing such functionality to the web at large.  Developing these features without much involvement from the Web community comes with the price of temporary proprietary APIs.    This clearly indicates their lack of standardization at that time and limits the number of developers relying upon them.  Mozilla will learn from efforts 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.