Index: source =================================================================== --- source (revision 6816) +++ source (working copy) @@ -95720,12 +95720,13 @@ body">after body", "in frameset", "after frameset", "after after body", and "after after body", "after after - frameset" during the course of the parsing, as described in - the tree construction stage. The insertion mode affects - how tokens are processed and whether CDATA sections are - supported.

+ frameset", and unknown context, during the course of + the parsing, as described in the tree construction + stage. The insertion mode affects how tokens are processed and + whether CDATA sections are supported.

Several of these modes, namely "in head", "in @@ -99861,7 +99862,52 @@ +

The "unknown context" insertion mode
+

When the user agent is to apply the rules for the "unknown context" insertion mode, the user agent must handle the token as follows:

+ +
+
A start tag whose tag name is one of: "caption", "colgroup", "tbody", "thead", "tfoot"
+
+

Process the token using the rules for the "in table" insertion + mode.

+ +
A start tag whose tag name is "tr"
+
+

Process the token using the rules for the "in table body" + insertion mode.

+ +
A start tag whose tag name is "col"
+
+

Process the token using the rules for the "in column group" + insertion mode.

+ +
A start tag whose tag name is one of: "td", "th"
+
+

Process the token using the rules for the "in table row" + insertion mode.

+ +
A start tag whose tag name is one of: "rp", "rt
+
+

If the stack of open elements has a ruby element in scope, + or if the stack of open elements is empty, then generate implied + end tags. + +

Insert an HTML element for the token. + +

Anything else
+
+

Process the token using the rules for the "in body" insertion + mode.

+
+
+
The "in body" insertion mode

When the user agent is to apply the rules for the "in body" insertion mode, the user agent must handle the token as follows:

@@ -101600,9 +101646,13 @@

When the steps above require the UA to clear the stack back to a table context, it means that the UA must, while the current node is not a table - element or an html element, pop elements from the + element, an html element, or empty, pop elements from the stack of open elements.

+

The current node being empty + after this process happens in the unknown context insertion + mode.

+

The current node being an html element after this process is a fragment case.

@@ -116550,4 +116600,4 @@ - \ No newline at end of file +