ExposureGuidelines: Difference between revisions

Jump to navigation Jump to search
→‎Email templates: Add code sample as discussed on m.d.platform
m (Fix up the removal of Firefox OS text)
(→‎Email templates: Add code sample as discussed on m.d.platform)
Line 92: Line 92:
* '''Security & Privacy Concerns''' - consider providing a link to answers in [https://mikewest.github.io/spec-questionnaire/security-privacy/ this security/privacy questionnaire] for a spec feature, if the spec doesn't already answer it. In particular, consider if the spec exposes new information about a user's computer or behavior that can contribute to fingerprinting.
* '''Security & Privacy Concerns''' - consider providing a link to answers in [https://mikewest.github.io/spec-questionnaire/security-privacy/ this security/privacy questionnaire] for a spec feature, if the spec doesn't already answer it. In particular, consider if the spec exposes new information about a user's computer or behavior that can contribute to fingerprinting.
* '''Web designer / developer use-cases''' AKA '''Why a developer would use Feature X?''' - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate why and when they would use this feature.
* '''Web designer / developer use-cases''' AKA '''Why a developer would use Feature X?''' - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate why and when they would use this feature.
* '''Example''' - Provide a brief code sample on how to use the API. Even with a formal specification, not everyone will know about the feature just from the name of the spec. An example will make it easier to understand how this feature can be used. This can either be an inline code sample, or a direct link to an example on the web.


==Intent to Ship==
==Intent to Ship==
Line 113: Line 114:


An Intent to Ship requires either a web platform test suite or such issues to be filed explaining why such a test suite is currently impossible or in the progress of being upstreamed.
An Intent to Ship requires either a web platform test suite or such issues to be filed explaining why such a test suite is currently impossible or in the progress of being upstreamed.
''Example'': Similar to the "intent to implement", provide a brief example on how the new feature can be used by a developer. This will help adoption and the reader does not have to skim the specification or bug patches to find a working example. This can either be a code sample, or a direct link to an example (e.g. bug comment or anchor within the specification).


==Intent to unship==
==Intent to unship==
258

edits

Navigation menu