mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-27 18:17:22 +02:00
a72fae8d36
Introduce a small set of counters on Document that track the work done while processing :has() invalidation: how often the upward walk runs, how many elements it visits, how often matches_has_pseudo_class() is invoked, how well the per-pass result cache performs, and how many elements transition from clean to needs-style-update. Expose the counters through internals so tests can assert precise bounds on the invalidation work triggered by a mutation, which regular reference tests cannot express. Add a css-has-invalidation test suite that covers subject-position, non-subject-position, sibling-combinator, and no-:has() cases. The baseline tests share a helper script so later coverage can reuse the same counter-printing path. The counters are test-only observation; they do not affect style computation itself.
25 lines
808 B
HTML
25 lines
808 B
HTML
<!DOCTYPE html>
|
|
<script src="../include.js"></script>
|
|
<script src="_helpers.js"></script>
|
|
<style>
|
|
.anchor:has(+ .match) { color: red; }
|
|
</style>
|
|
<div id="a1">
|
|
<div id="a2">
|
|
<span id="anchor" class="anchor">anchor</span>
|
|
<span id="target">target</span>
|
|
</div>
|
|
</div>
|
|
<script>
|
|
test(() => {
|
|
getComputedStyle(document.getElementById("anchor")).color;
|
|
internals.resetStyleInvalidationCounters();
|
|
|
|
// Sibling combinator in :has(). Anchor has sibling-combinator flag,
|
|
// so invalidation must also walk siblings of each visited ancestor.
|
|
document.getElementById("target").classList.add("match");
|
|
getComputedStyle(document.getElementById("anchor")).color;
|
|
printCounters("after add .match on adjacent sibling");
|
|
});
|
|
</script>
|