canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
s/browser vendor/browser engine
(s/browser vendor/browser engine) |
|||
| Line 17: | Line 17: | ||
# the relevant standards body declares it ready for implementation | # the relevant standards body declares it ready for implementation | ||
# at least two other browser | # at least two other browser engines ship a compatible implementation of this API | ||
# at least one other browser | # at least one other browser engines ships -- or publicly states their intention to ship -- a compatible implementation of this API and there is a specification that is no longer at risk of significant changes, on track to become a standard with an relevant standards body, and acceptable to a number of applicable parties | ||
==Exceptions== | ==Exceptions== | ||
Exceptions to the standardization rules above include: | Exceptions to the standardization rules above include: | ||
# during the first 12 months of development of new user-facing products, APIs that have not yet been embraced by other | # during the first 12 months of development of new user-facing products, APIs that have not yet been embraced by other browser engines or thoroughly discussed by standards bodies may be shipped '''only as a part of this product''', thus clearly indicating their lack of standardization and limiting any market share they may attain | ||
# ecosystem- and hardware-specific APIs that are not standard or of interest to the broader web at that time (or ever) may be shipped in a way to limit their harm of the broader web (ex. only on a device or only in specific builds with clear disclaimers about applicability of exposed APIs). An example of this is the FM Radio API for Firefox OS. | # ecosystem- and hardware-specific APIs that are not standard or of interest to the broader web at that time (or ever) may be shipped in a way to limit their harm of the broader web (ex. only on a device or only in specific builds with clear disclaimers about applicability of exposed APIs). An example of this is the FM Radio API for Firefox OS. | ||
# APIs solving use cases which no browser vendor shipping an engine other than Gecko is interested in at that time. In cases such as this, Mozilla will solicit feedback from as many relevant parties as possible, begin the standardization process with a relevant standards body, and create a test suite as part of the standards process. An example of this is the Push Notifications API. | # APIs solving use cases which no browser vendor shipping an engine other than Gecko is interested in at that time. In cases such as this, Mozilla will solicit feedback from as many relevant parties as possible, begin the standardization process with a relevant standards body, and create a test suite as part of the standards process. An example of this is the Push Notifications API. | ||