Platform/Proposing Gecko Features
Proposing Web-Platform Features for Gecko
This page explains what's required to propose that a web-platform feature is implemented in Gecko.
If you want Mozilla's feedback on a new platform feature you should not file an implementation bug, but make a standards-position request.
Creating Feature Proposals
All feature proposals in Gecko are tracked by a bug in Bugzilla.
This bug must be filed in the relevant product (usually Core) and component for the feature. In the rare case that there's no existing component for the feature, it can be filed under the Core product in the General component.
On filing bugs should have as much of the following information as possible:
Title:
- Of the form
[meta] Implement {feature name}
Description:
- A short summary of the purpose of a feature. This can generally be very brief and does not need to restate in detail information that's in the corresponding standards-position request, specification document, or explainer.
Type:
enhancement
In the URL field: A link to the relevant specification for the feature. If more than one link is required additional links can be added to the ```See Also``` field
In the See Also field:
- A link to the GitHub issue for the Mozilla standards-position request relating to the feature (if any)
- A link to the GitHub issue for WebKit standards-position request relating to the feature (if any)
- wpt.fyi links for any web-platform-tests covering the feature (if known)
In the User Story field:
- If the feature corresponds to a single web-feature then a line containing the string
web-feature:{feature-id}
In the Whiteboard field:
- The string
[platform-feature]
In the Keywords field:
parity-chromeif the feature is already implemented in Chromeparity-safariif the feature is already implemented in Safari