ladybird/Tests/LibWeb/Text/expected/DOM/Node-lookupNamespaceURI.txt
Timothy Flynn bf668696de LibWeb+WebContent: Do not include DOM HTML in text test expectations
For example, in the following abbreviated test HTML:

    <span>some text</span>
    <script>println("whf")</script>

We would have to craft the expectation file to include the "some text"
segment, usually with some leading whitespace. This is a bit annoying,
and makes it difficult to manually craft expectation files.

So instead of comparing the expectation against the entire DOM inner
text, we now send the inner text of just the <pre> element containing
the test output when we invoke `internals.signalTextTestIsDone`.
2024-10-03 07:07:28 -04:00

20 lines
931 B
Text

documentFragment.lookupNamespaceURI(null): null
documentFragment.lookupNamespaceURI(""): null
documentFragment.lookupNamespaceURI("foo"): null
documentFragment.lookupNamespaceURI("xml"): null
documentFragment.lookupNamespaceURI("xmlns"): null
docType.lookupNamespaceURI(null): null
docType.lookupNamespaceURI(""): null
docType.lookupNamespaceURI("foo"): null
docType.lookupNamespaceURI("xml"): null
docType.lookupNamespaceURI("xmlns"): null
element.lookupNamespaceURI(null): null
element.lookupNamespaceURI(""): null
element.lookupNamespaceURI("foo"): null
element.lookupNamespaceURI("xml"): http://www.w3.org/XML/1998/namespace
element.lookupNamespaceURI("xmlns"): http://www.w3.org/2000/xmlns/
After setting element attribute xmlns:bar='exampleNamespaceURI'
element.lookupNamespaceURI(null): null
element.lookupNamespaceURI(""): null
element.lookupNamespaceURI("foo"): null
element.lookupNamespaceURI("bar"): exampleNamespaceURI