This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The harness should use the flags field to look up messages (in a separate flag-message mapping table) and display them in the notes field. (First action's on me to write a sample map.)
This is currently the case. The current flag-message mapping table is as follows: flag description --------- ------------------------ ahem Requires the Ahem font dom Requires support for JavaScript and the Document Object Model (DOM) font Requires a specific font to be installed. (Details must be provided and/or the font linked to in the test description) history User agent session history is required. Testing :visited is a good example where this may be used. HTML only Test case is only valid for HTML image Requires support for bitmap graphics and the graphic to load interact Requires human interaction (such as for testing scrolling behavior) invalid Tests handling of invalid CSS. Note: This case contains CSS properties and syntax that my not validate. namespace Requires support for XML Namespaces nonHTML Test case is only valid for formats besides HTML (e.g. XHATML or arbitrary XML) may Behavior tested is preferred but OPTIONAL. [RFC2119] (These tests must be reviewed by a test suite owner or peer.) paged Only valid for paged media should Behavior tested is RECOMMENDED, but not REQUIRED. [RFC2119] scroll Only valid for continuous (scrolling) media svg Requires support for vector graphics (SVG) 96dpi Assumes 96dpi display Please revise as desired.
Unless I have misunderstood this bug or unless there are any edits to the mapping table, this should be marked resolved. I'll wait until the next code check in. Probably Monday or Tuesday.