diff --git a/source b/source index 91a98c390ef..2472f5a9cdb 100644 --- a/source +++ b/source @@ -114897,28 +114897,27 @@ enum DOMParserSupportedType { context and a string markup, are:

    -

  1. Let algorithm be the HTML fragment parsing algorithm.

    2. +

  2. Let algorithm be the HTML fragment parsing algorithm.

    3. -

  3. If context's node document is an XML document, then set algorithm to the XML fragment parsing - algorithm.

    4. +

  4. If context's node document is an XML + document, then set algorithm to the XML fragment parsing + algorithm.

    5. -

  5. Let new children be the result of invoking algorithm given - markup, with context set to - context.

    6. +

  6. Let newChildren be the result of invoking algorithm given + context and markup.

    7. -

  7. Let fragment be a new DocumentFragment whose node - document is context's node document.

    8. +

  8. Let fragment be a new DocumentFragment whose node + document is context's node document.

    9. -
  9. -

    Append each Node in new - children to fragment (in tree order).

    +
  10. +

    For each node of newChildren, in tree order: append node to fragment.

    -

    This ensures the node document for the new nodes is correct.

    -
    11. +

    This ensures the node document for the new nodes is correct.

    + -

  11. Return fragment.

    12. +

  12. Return fragment.

Element's Parsing HTML fragments -

The following steps form the HTML fragment parsing algorithm. The algorithm - takes as input an Element node, referred to as the context element, which gives the context for - the parser, input, a string to parse, and an optional boolean - allowDeclarativeShadowRoots (default false). It returns a list of zero or more - nodes.

- -

Parts marked fragment case in algorithms in the parser section are - parts that only occur if the parser was created for the purposes of this algorithm. The algorithms have been annotated - with such markings for informational purposes only; such markings have no normative weight. If it - is possible for a condition described as a fragment case to occur even when the - parser wasn't created for the purposes of handling this algorithm, then that is an error in the - specification.

+

The HTML fragment parsing algorithm given an Element node context, string input, and an + optional boolean allowDeclarativeShadowRoots (default false) are the following steps. + They return a list of zero or more nodes.

+ +

Parts marked fragment case in algorithms in the HTML + parser section are parts that only occur if the parser was created for the purposes of this + algorithm. The algorithms have been annotated with such markings for informational purposes only; + such markings have no normative weight. If it is possible for a condition described as a + fragment case to occur even when the parser wasn't created for the purposes of + handling this algorithm, then that is an error in the specification.

    -
  1. -

    Create a new Document node, and mark it as being an HTML document.

    -
    2. +

  2. Let document be a Document node whose type is "html".

    3. -
  3. -

    If the - node document of the context element is in - quirks mode, then let the Document be in quirks mode. - Otherwise, if the - node document of the context element is in - limited-quirks mode, then let the Document be in limited-quirks - mode. Otherwise, leave the Document in no-quirks mode.

    -
    4. +

  4. If context's node document is + in quirks mode, then set document's mode to "quirks".

    5. -

  5. If allowDeclarativeShadowRoots is true, then set the Document's - allow declarative shadow - roots to true.

    6. +

  6. Otherwise, if context's node + document is in limited-quirks mode, then set document's mode to "limited-quirks".

    7. -
  7. -

    Create a new HTML parser, and associate it with the just created - Document node.

    -
    8. +

  8. If allowDeclarativeShadowRoots is true, then set document's allow declarative shadow roots to + true.

    9. + +

  9. Create a new HTML parser, and associate it with document.

  10. Set the state of the HTML parser's tokenization stage as follows, switching on the context element:

    -
    title
    textarea
    -
    Switch the tokenizer to the RCDATA state.
    -
    style
    xmp
    iframe
    noembed
    noframes
    -
    Switch the tokenizer to the RAWTEXT state.
    -
    script
    -
    Switch the tokenizer to the script data state.
    -
    noscript
    -
    If the scripting flag is enabled, switch the tokenizer to the RAWTEXT state. Otherwise, leave the tokenizer in the data state.
    -
    plaintext
    -
    Switch the tokenizer to the PLAINTEXT state.
    -
    Any other element
    -
    Leave the tokenizer in the data state.
    @@ -134364,35 +134342,29 @@ console.assert(container.firstChild instanceof SuperP); transitions.

    11. -
  11. -

    Let root be a new html element with no attributes.

    -
    12. +

  12. Let root be the result of creating an + element given document, "html", and the HTML + namespace.

    13. -
  13. -

    Append the element root to the Document node created - above.

    -
    14. +

  14. Append root to + document.

    15. -
  15. -

    Set up the parser's stack of open elements so that it contains just the single - element root.

    -
    16. +

  16. Set up the HTML parser's stack of open elements so that it + contains just the single element root.

    17. -
  17. -

    If the context element is a - template element, push "in - template" onto the stack of template insertion modes so that it is the new - current template insertion mode.

    -
    18. +

  18. If context is a template + element, then push "in template" onto the + stack of template insertion modes so that it is the new current template + insertion mode.

  19. Create a start tag token whose name is the local name of context and whose attributes are the attributes of context.

    -

    Let this start tag token be the start tag token of the context node, e.g. for the purposes of determining - if it is an HTML integration point.

    +

    Let this start tag token be the start tag token of context, e.g. for the purposes of determining if it is + an HTML integration point.

  20. @@ -134403,29 +134375,22 @@ console.assert(container.firstChild instanceof SuperP); data-x="concept-frag-parse-context">context element as part of that algorithm.

    21. -
  21. -

    Set the parser's form element pointer to the nearest node to the - context element that is a form - element (going straight up the ancestor chain, and including the element itself, if it is a - form element), if any. (If there is no such form element, the - form element pointer keeps its initial value, null.)

    -
    22. +

  22. Set the HTML parser's form element pointer to the + nearest node to context that is a + form element (going straight up the ancestor chain, and including the element + itself, if it is a form element), if any. (If there is no such form + element, the form element pointer keeps its initial value, + null.)

    23. -
  23. -

    Place the input into the input stream for the HTML - parser just created. The encoding confidence is irrelevant.

    -
    24. +

  24. Place the input into the input stream for the HTML + parser just created. The encoding confidence is irrelevant.

    25. -
  25. -

    Start the parser and let it run until it has consumed all the characters just inserted into - the input stream.

    -
    26. +

  26. Start the HTML parser and let it run until it has consumed all the characters + just inserted into the input stream.

    27. -
  27. -

    Return the child - nodes of root, in tree order.

    -
    28. +

  28. Return root's children, in tree + order.

@@ -134739,22 +134704,18 @@ console.assert(container.firstChild instanceof SuperP);

Parsing XML fragments

-

The XML fragment parsing algorithm either returns a Document or throws - a "SyntaxError" DOMException. Given a string - input and a context element context, the - algorithm is as follows:

+

The XML fragment parsing algorithm given an Element node context and a string input, runs the + following steps. They return a list of nodes.

    -
  1. -

    Create a new XML parser.

    -
    2. +

  2. Create a new XML parser.

  3. -

    Feed the - parser just created the string corresponding to the start tag of the context element, declaring - all the namespace prefixes that are in scope on that element in the DOM, as well as declaring - the default namespace (if any) that is in scope on that element in the DOM.

    +

    Feed the parser just created the string corresponding to the start tag of context, declaring all the namespace prefixes that are + in scope on that element in the DOM, as well as declaring the default namespace (if any) that is + in scope on that element in the DOM.

    A namespace prefix is in scope if the DOM lookupNamespaceURI() method on the element would return a non-null value for that prefix.

    @@ -134762,34 +134723,26 @@ console.assert(container.firstChild instanceof SuperP);

    The default namespace is the namespace for which the DOM isDefaultNamespace() method on the element would return true.

    -

    No - DOCTYPE is passed to the parser, and therefore no external subset is - referenced, and therefore no entities will be recognized.

    -
    4. - -
  4. -

    Feed the parser just created the string input.

    +

    No DOCTYPE is passed to the parser, and therefore no + external subset is referenced, and therefore no entities will be recognized.

    5. -
  5. -

    Feed the parser just created the string corresponding to the end tag of the context element.

    -
    6. +

  6. Feed the parser just created the string input.

    7. -
  7. -

    If there is an XML well-formedness or XML namespace well-formedness error, then throw a - "SyntaxError" DOMException.

    -
    8. +

  8. Feed the parser just created the string corresponding to the end tag of context.

    9. -
  9. -

    If the document element of the resulting Document has any sibling - nodes, then throw a "SyntaxError" DOMException.

    +

  10. If there is an XML well-formedness or XML namespace well-formedness error, then throw a + "SyntaxError" DOMException.

    11. - - +

  11. If the document element of the resulting Document has any + sibling nodes, then throw a "SyntaxError" + DOMException.

    12. + -

  12. Return the child nodes of the document element of the resulting - Document, in tree order.

    13. +

  13. Return the resulting Document node's document element's children, in tree order.