ExposureGuidelines: Difference between revisions

m (Typo: will believe -> believe to/will be)
Line 27: Line 27:
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.  Products such as Firefox OS would ship these APIs as a part of their product but not to the broader web, thus clearly indicating their lack of standardization and limiting the number of web developers relying upon them.  When rare situations such as this arise, '''API standardization must begin within one year of shipping''' the initial version of such products.
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.  Products such as Firefox OS would ship these APIs as a part of their product but not to the broader web, thus clearly indicating their lack of standardization and limiting the number of web developers relying upon them.  When rare situations such as this arise, '''API standardization must begin within one year of shipping''' the initial version of such products.


Since APIs will very likely change as they are standardized and some developers will build things on top of non-standardized versions of these APIs, we will try to assist affected developers to an appropriate extent, with the extent of our efforts made on a case-by-case basis.  Should an API's standardization process fail, it is unclear what will be done with the non-standard API that has been shipped since some people will surely be relying upon it, even if it is only a part of one product and not available to the web at large.  '''FIXME''' should we ship these APIs prefixed or under a window.mozilla namespace or just with their "normal" name?
Since APIs will very likely change as they are standardized and some developers will build things on top of non-standardized versions of these APIs, we will try to reasonably assist affected developers where possible.  Should an API's standardization process fail, it is unclear what will be done with the non-standard API that has been shipped since some people will surely be relying upon it, even if it is only a part of one product and not available to the web at large.  '''FIXME''' should we ship these APIs prefixed or under a window.mozilla namespace or just with their "normal" name?


=Implementation Process=
=Implementation Process=
canmove, Confirmed users
901

edits