Bugzilla conventions

These are the conventions used for bugs filed in the W3C Bugzilla for specs also maintained by the WHATWG.

Subject prefixes

Some specific topics have prefixes in the bug summaries to help group the bugs.

<video>

bugs relating to <video>, <audio>, HTMLMediaElement, Controller, WebVTT, WebRTC (PeerConnection and Stream), and closely related topics.

WF2:

bugs relating to form controls.

WF3:

feature requests relating to form controls.

PUB:

something relating to the spec publication process (including anolis, spec splitter, the START and END markers, etc)

Priorities and Severities

All bugs should be P2 or P3 by default. Bugs might get marked P1 by the W3C HTML WG chairs; bugs marked P1 by anyone else should be returned to P3. Bugs that are particularly minor might be marked P5. The priority field is "owned" by the chairs.

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.

Components

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.

Resolutions

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:

http://dev.w3.org/html5/decision-policy/decision-policy-v2.html#bug-resolutions

Helpful query links

• 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.