These are the conventions used for bugs filed in the W3C Bugzilla for specs also maintained by the WHATWG.
Some specific topics have prefixes in the bug summaries to help group the bugs.
- bugs relating to <video>, <audio>, HTMLMediaElement, Controller, WebVTT, WebRTC (PeerConnection and Stream), and closely related topics.
- bugs relating to form controls.
- feature requests relating to form controls.
- something relating to the spec publication process (including anolis, spec splitter, the START and END markers, etc)
See bug priority policy according to the chairs. Initial commenters are only allowed to set priority to P3 or lower. Editors and editorial assistants can change it freely. Chairs can decide on a final priority. P1 is very urgent. P2 or P3 is for technical comments except possibly feature requests. P4 or P5 is editorial or non-technical, or feature requests.
All bugs should be normal severity by default. Typos, grammar mistakes that don't affect normative status, and other such trivial matters can be marked "trivial". Feature requests should be marked "enhancement". Bugs that affect the parser algorithm should be marked "critical". Bugs that are immediately affecting implementors should be marked "blocker". "major" and "minor" are currently unused. The severity field is "owned" by the editor.
The bug filing system should automatically pick the right component. The components are pretty self-explanatory. WHATWG-specific issues should be moved to the "other Hixie drafts" component.
The boilerplate used when resolving the bug comes from: http://lists.w3.org/Archives/Public/public-html/2009Oct/0680.html
The requirements for use of different resolutions are here:
- List of all open and deferred HTML-related bugs
- List of LATERed bugs. Some of these are commonly duped. In particular bug 7798 is TextMetrics.height which is often requested.
- List of all open bugs in specs edited by Hixie, sorted by ascending last change time
If you're helping with the bugs you may find these bookmarlets useful.