Skip to content

fix: match no node inside a template, as a browser does - #8

Merged
sorge-it merged 1 commit into
mainfrom
fix/template-content
Oct 6, 2026
Merged

sorge-it merged 1 commit into
mainfrom
fix/template-content

Conversation

@sorge-it

@sorge-it sorge-it commented Oct 6, 2026

Copy link
Copy Markdown
Owner

A selector found a node inside a <template>, though the page does not show it, so a check could pass on markup that only a script would render. attributeValues() leaves those nodes out too. The <template> element itself still matches. A test covers it; two mutations turn it red. See CHANGELOG.md, section 1.4.2.

A selector found a node inside a template, though the page does not show it, so a check could pass on markup only a script would render. attributeValues() leaves those out too.
@sorge-it
sorge-it merged commit 8fc48fe into main Oct 6, 2026
3 checks passed
@sorge-it
sorge-it deleted the fix/template-content branch October 6, 2026 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant