ExposureGuidelines: Difference between revisions

→‎Intent to Implement: Move tests / other engines lines up, as they're usually ignored
(Note that the bug "intent to ship" emails reference should have 'dev-doc-needed' keyword set)
(→‎Intent to Implement: Move tests / other engines lines up, as they're usually ignored)
Line 60: Line 60:
''Estimated or target release'':  in which version do you want to/plan to release this?<br />
''Estimated or target release'':  in which version do you want to/plan to release this?<br />
''Preference behind which this will be implemented'':  if applicable, how can interested parties test this before it ships pref'd on by default?<br />
''Preference behind which this will be implemented'':  if applicable, how can interested parties test this before it ships pref'd on by default?<br />
''DevTools bug'':  link to a Firefox :: Developer Tools bug coordinating work with the DevTools team to build tools for this feature
''DevTools bug'':  link to a Firefox :: Developer Tools bug coordinating work with the DevTools team to build tools for this feature<br />
''Do other browser engines implement this?'' Answer with: Shipped (since version X, behind what flags if any), Intent to implement emailed (mailing list URL), Considering (citation)<br />
''Tests'' - URLs / paths to tests (preferably web-platform-tests)


=== Suggested Additions ===
=== Suggested Additions ===
Line 66: Line 68:


If you're looking for extra credit, or to preempt common questions, consider adding any or all of the following (all based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails).
If you're looking for extra credit, or to preempt common questions, consider adding any or all of the following (all based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails).
* '''Do other browser engines implement this?''' Answer with:
** Shipped (since version X, behind what flags if any), Intent to implement emailed (mailing list URL), Considering (citation)
* '''Tests''' - URLs / paths to tests
* '''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.
* '''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.
* '''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.
Confirmed users
97

edits