Critical HTML5 sections for CR exit criteria still in need of tests

In preparation for the HTML WG TPAC agenda item to discuss testing status for HTML5 [1], Denis and I put together a list of sections in the spec which currently have no tests whatsoever, but were identified by the WG as areas requiring testing in order to satisfy CR exit criteria [2]. We did this by identifying which subsections of the HTML5 spec didn't yet have test representation in web-platform-tests [3], and then comparing that list to the subsections marked as "Requires testing" and "Has implementations [but no tests]" in the "Overview of testing in view of CR exit" [2] document.
Please note that a section marked "Requires testing" or "Has implementations [but no tests]" that is not listed here doesn't necessarily mean that we have sufficient test coverage for it (that has yet to be assessed). The list below is simply meant to report on areas for which we already know we'll need a concentrated testing effort. They are roughly grouped by chapter.

HTML5 and Canvas2D testing status will be further discussed during the F2F meetings coming up shortly.




2.5.2 Resolving URLs
2.5.3 Dynamic changes to base URLs

3.1.1 The Document object
3.1.2 Security
3.1.5 Loading XML documents

4.2.3 The base element
4.6.21 The ruby element
4.6.22 The rt element
4.6.23 The rp element
4.6.25 The bdo element
4.6.28 The wbr element	
4.7.1 The ins element
4.7.2 The del element
4.7.3 Attributes common to ins and del elements
4.7.4 Edits and paragraphs
4.7.5 Edits and lists
4.7.6 Edits and tables
4.8.2 The iframe element
4.8.3 The embed element
4.8.4 The object element
4.8.5 The param element
4.8.9 The track element

Other namespaces
4.8.15 MathML
4.8.16 SVG

4.10.4 The fieldset element
4.10.8 The button element
4.10.10 The datalist element
4.10.17 The meter element
4.14 Disabled elements
4.15.1 Case-sensitivity
4.15.2 Pseudo-classes

Browsing contexts
5.1.3 Secondary browsing contexts
5.1.4 Security
5.1.5 Groupings of browsing contexts
5.1.6 Browsing context names

5.2.1 Security
5.2.2 APIs for creating and navigating browsing contexts by name
5.2.3 Accessing other browsing contexts
5.2.5 Garbage collection and browsing contexts
5.2.6 Closing browsing contexts
5.2.7 Browser interface elements
5.2.8 The WindowProxy object

5.3.1 Relaxing the same-origin restriction

5.4 Sandboxing

5.5.1 The session history of browsing contexts
5.5.4 Implementation notes for session history

5.6.1 Navigating across documents
5.6.2 Page load processing model for HTML files
5.6.3 Page load processing model for XML files
5.6.5 Page load processing model for multipart/x-mixed-replace resources
5.6.7 Page load processing model for content that uses plugins
5.6.8 Page load processing model for inline content that doesn't have a DOM
5.6.9 Navigating to a fragment identifier
5.6.12 Aborting a document load

7.4.1 Sequential focus navigation and the tabindex attribute
7.4.2 Focus management
7.4.3 Document-level focus APIs
7.4.4 Element-level focus APIs

Keyboard shortcuts
7.5.1 Introduction
7.5.2 The accesskey attribute
7.5.3 Processing model
7.6.3 Best practices for in-page editors
7.6.4 Editing APIs

Drag and drop
7.7.1 Introduction
7.7.2 The drag data store
7.7.4 The DragEvent interface
7.7.5 Drag-and-drop processing model
7.7.6 Events summary
7.7.7 The draggable attribute
7.7.8 The dropzone attribute
7.7.9 Security risks in the drag-and-drop model

XHTML syntax
9.3 Serializing XHTML fragments
9.4 Parsing XHTML fragments

Received on Thursday, 14 November 2013 00:33:46 UTC