canmove, Confirmed users
2,885
edits
ExposureGuidelines: Difference between revisions
Jump to navigation
Jump to search
→Intent to Implement: move suggested additions here per Andrew Overholt email suggestion
(see also) |
(→Intent to Implement: move suggested additions here per Andrew Overholt email suggestion) |
||
| 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 /> | ||
=== Suggested Additions === | |||
The above is the minimum required that should be in an "Intent to implement" email. If you've covered those, you're good, and brevity is a virtue. | |||
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''' | |||
* '''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. | |||
==Intent to Ship== | ==Intent to Ship== | ||