ExposureGuidelines: Difference between revisions

ExposureGuidelines (view source)

21 bytes added , 21 June 2013

canmove, Confirmed users

901

edits

@@ Line 2: / Line 2: @@
 =Goal=
-Mozilla aims to advance the state of the open web with new features, enhanced security, and the removal of unnecessary cruft.  We will not hurt the web by exposing an API in such a way that a web developer can detect it ([https://groups.google.com/a/chromium.org/d/msg/chromium-dev/HN2e4sGbVus/OIEWgN1yi04J 1]) before it's ready.  In the past we have shipped APIs with "moz" prefixes to indicate their lack of standardization but we will no longer do this (see [https://groups.google.com/forum/#!topic/mozilla.dev.platform/34JfwyEh5e4 Henri Sivonen's proposal]).  Note that at this time, we are specifically focusing on JS APIs and not on other web-facing properties (ex. CSS).
+Mozilla aims to advance the state of the open web with new features, enhanced security, and the removal of unnecessary cruft.  We will not hurt the web by exposing an API in such a way that a web developer can detect it ([https://groups.google.com/a/chromium.org/d/msg/chromium-dev/HN2e4sGbVus/OIEWgN1yi04J 1]) before it's ready.  In the past we have shipped APIs with "moz" prefixes to indicate their lack of standardization but we will no longer do this (see [https://groups.google.com/forum/#!topic/mozilla.dev.platform/34JfwyEh5e4 Henri Sivonen's proposal]).  Note that at this time, we are specifically focusing on JS APIs and not on other web-facing features/properties such as CSS and WebGL.
 =Process Overview=