Confirmed users
112
edits
ExposureGuidelines: Difference between revisions
Jump to navigation
Jump to search
→Guidelines for Mozillians developing new features: link Modules; remove obsolete page
(→Suggested implementation process: add secure contexts requirement) |
(→Guidelines for Mozillians developing new features: link Modules; remove obsolete page) |
||
| Line 8: | Line 8: | ||
=Guidelines for Mozillians developing new features= | =Guidelines for Mozillians developing new features= | ||
The following is put forward as a set of guidelines for Mozillians -- especially module owners and peers -- to refer to while developing new APIs for the Web. The primary question that must be asked is: | The following is put forward as a set of guidelines for Mozillians -- especially [[Modules|module owners and peers]] -- to refer to while developing new APIs for the Web. The primary question that must be asked is: | ||
::''Is this good for the web?'' | ::''Is this good for the web?'' | ||
| Line 44: | Line 44: | ||
# [https://blog.mozilla.org/security/2018/01/15/secure-contexts-everywhere/ Restrict the feature to secure contexts]. | # [https://blog.mozilla.org/security/2018/01/15/secure-contexts-everywhere/ Restrict the feature to secure contexts]. | ||
# Land potentially disruptive features behind a preference which is off by default. | # Land potentially disruptive features behind a preference which is off by default. | ||
==Turning a preference on by default== | ==Turning a preference on by default== | ||
When you are satisfied that your new feature is stable enough for exposure to the web at large (see [[#When is a feature ready to be shipped by Gecko?|above]]), it is requested that implementers send another email to dev-platform declaring their [[#Intent to ship|intent to ship]]. Among other things, this email serves to inform those that are interested in the new API but have not been closely following the implementation bug(s). | When you are satisfied that your new feature is stable enough for exposure to the web at large (see [[#When is a feature ready to be shipped by Gecko?|above]]), it is requested that implementers send another email to dev-platform declaring their [[#Intent to ship|intent to ship]]. Among other things, this email serves to inform those that are interested in the new API but have not been closely following the implementation bug(s). | ||
=Guidelines for removing features= | =Guidelines for removing features= | ||