Create nodes in the realm of the document they are created for#12669
Merged
Conversation
Follow DOM in creating parsed nodes in the relevant realm of their node document rather than the realm running the parser, resolving a cross-browser interoperability issue. Depends on whatwg/dom#1491.
sideshowbarker
approved these changes
Jul 17, 2026
annevk
added a commit
to whatwg/dom
that referenced
this pull request
Jul 17, 2026
Which realm a node is created in was unspecified, so implementations disagreed when a node was created for a document whose relevant realm differed from the one running the algorithm (e.g., parsing, importing, or cloning into an adopted node's document). This also makes the HTML parser initialize processing instructions, populating their attribute map as createProcessingInstruction() and the constructor already did. Tests: web-platform-tests/wpt#61212 HTML PR: whatwg/html#12669 Fixes #977.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow DOM in creating parsed nodes in the relevant realm of their node document rather than the realm running the parser, resolving a cross-browser interoperability issue.
Depends on whatwg/dom#1491.
(See WHATWG Working Mode: Changes for more details.)
/common-dom-interfaces.html ( diff )
/dom.html ( diff )
/dynamic-markup-insertion.html ( diff )
/form-elements.html ( diff )
/infrastructure.html ( diff )
/parsing.html ( diff )
/scripting.html ( diff )
/xhtml.html ( diff )