Confirmed users
29
edits
ExposureGuidelines: Difference between revisions
Remove mention of Firefox OS
(→Intent to Implement: Move tests / other engines lines up, as they're usually ignored) |
(Remove mention of Firefox OS) |
||
| Line 5: | Line 5: | ||
==Special Cases== | ==Special Cases== | ||
There may be special cases where we deviate from this goal. | 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. | ||
=Guidelines for Mozillians developing new APIs= | =Guidelines for Mozillians developing new APIs= | ||
| Line 57: | Line 57: | ||
''Bug'': link to main implementation tracking bug<br /> | ''Bug'': link to main implementation tracking bug<br /> | ||
''Link to standard'': if no formal specification exists yet, link to public discussions with other browser vendors<br /> | ''Link to standard'': if no formal specification exists yet, link to public discussions with other browser vendors<br /> | ||
''Platform coverage'': where will this be available? Android, Desktop | ''Platform coverage'': where will this be available? Android, Desktop, only exposed to privileged apps (certified app-only functionality does not require an email), etc.<br /> | ||
''Estimated or target release'': in which version do you want to/plan to release this?<br /> | ''Estimated or target release'': in which version do you want to/plan to release this?<br /> | ||
''Preference behind which this will be implemented'': if applicable, how can interested parties test this before it ships pref'd on by default?<br /> | ''Preference behind which this will be implemented'': if applicable, how can interested parties test this before it ships pref'd on by default?<br /> | ||