Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2026-04-19 18:30:27 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Tests/LibWeb/Text/input/hit_testing/pointer-events.html

53 lines
2 KiB
HTML
Raw Normal View History

Meta: Add DOCTYPEs to most text tests
2025-03-18 19:28:35 +01:00
<!DOCTYPE html>
LibWeb: Reorder paintable hit-testing to account for `pointer-events` Instead of ignoring any paintable immediately when they're invisible to hit-testing, consider every candidate and while the most specific candidate is invisible to hit-testing, traverse up to its parent paintable. This more closely reflects the behavior expected when wrapping block elements inside inline elements, where although the block element might have `pointer-events: none`, it still becomes part of the hit-test body of the inline parent. This makes the following link work as expected: <a href="https://ladybird.org"> <div style="pointer-events: none">Ladybird</div> </a>
2025-01-21 15:24:46 +01:00
<script src="../include.js"></script>
<body>
<!-- #a2 should be invisible to hit testing -->
<div id="a1">
<div id="a2" style="width: 100px; height: 100px; pointer-events: none"></div>
</div>
<!-- #b3 should be visible to hit testing -->
<div id="b1">
<div id="b2" style="width: 100px; height: 100px; pointer-events: none">
<div id="b3" style="width: 100px; height: 100px; pointer-events: auto"></div>
</div>
</div>
<!-- #c1 should be hit, even though it is an inline element surrounding a block element -->
<a id="c1">
<div id="c2" style="width: 100px; height: 100px; pointer-events: none"></div>
</a>
<!-- a pointer event on #d4 should hit #d2 instead -->
<b id="d1">foo<i id="d2"><div id="d3">bar</div>baz<u id="d4" style="pointer-events: none">lorem</u></i></b>
LibWeb: Honor `pointer-events` for PaintableBox in own stacking context If a block element with its own stacking context has `pointer-events: none` set, it should be ignored as far as hit-testing goes. Fixes #3357.
2025-01-25 22:41:21 +01:00
<!-- div creates its own stacking context, #e2 must be hit instead of crashing -->
<div id="e1" style="position: fixed; width: 100px; height: 100px; pointer-events: none; background-color: red"></div>
<div id="e2" style="width: 100px; height: 100px; background-color: green"></div>
LibWeb: Ignore fragments with `pointer-events: none` in hit-testing
2025-01-31 11:17:46 +01:00
<!-- #f1 must be hit instead of #f2 -->
<a id="f1"><img id="f2" style="height: 30px; width: 30px; pointer-events: none"></a>
LibWeb: Hit test StackingContext's children before testing visibility If a node that establishes a StackingContext has `pointer-events: none`, hit testing should first proceed with hit testing the SC's children before deciding to bail. We were checking for `pointer-events` too early, causing large parts of certain websites to be noninteractive. Fixes #6017.
2025-08-29 00:44:48 +02:00
<!-- div is positioned and creates its own stacking context, #g2 must be hit -->
<div id="g1" style="pointer-events: none; position: relative; z-index: 0"><a id="g2" style="pointer-events: auto">ladybird</a></div>
LibWeb: Reorder paintable hit-testing to account for `pointer-events` Instead of ignoring any paintable immediately when they're invisible to hit-testing, consider every candidate and while the most specific candidate is invisible to hit-testing, traverse up to its parent paintable. This more closely reflects the behavior expected when wrapping block elements inside inline elements, where although the block element might have `pointer-events: none`, it still becomes part of the hit-test body of the inline parent. This makes the following link work as expected: <a href="https://ladybird.org"> <div style="pointer-events: none">Ladybird</div> </a>
2025-01-21 15:24:46 +01:00
</body>
<script>
test(() => {
LibWeb: Hit test StackingContext's children before testing visibility If a node that establishes a StackingContext has `pointer-events: none`, hit testing should first proceed with hit testing the SC's children before deciding to bail. We were checking for `pointer-events` too early, causing large parts of certain websites to be noninteractive. Fixes #6017.
2025-08-29 00:44:48 +02:00
const printHit = (element, x, y) => {
const rect = element.getBoundingClientRect();
const hit = internals.hitTest(rect.x + x, rect.y + y);
LibWeb: Reorder paintable hit-testing to account for `pointer-events` Instead of ignoring any paintable immediately when they're invisible to hit-testing, consider every candidate and while the most specific candidate is invisible to hit-testing, traverse up to its parent paintable. This more closely reflects the behavior expected when wrapping block elements inside inline elements, where although the block element might have `pointer-events: none`, it still becomes part of the hit-test body of the inline parent. This makes the following link work as expected: <a href="https://ladybird.org"> <div style="pointer-events: none">Ladybird</div> </a>
2025-01-21 15:24:46 +01:00
printElement(hit.node);
printElement(hit.node.parentNode);
println('---');
};
LibWeb: Hit test StackingContext's children before testing visibility If a node that establishes a StackingContext has `pointer-events: none`, hit testing should first proceed with hit testing the SC's children before deciding to bail. We were checking for `pointer-events` too early, causing large parts of certain websites to be noninteractive. Fixes #6017.
2025-08-29 00:44:48 +02:00
printHit(a1, 50, 50);
printHit(b1, 50, 50);
printHit(c2, 50, 50);
printHit(d4, 10, 8);
printHit(e1, 50, 50);
printHit(f1, 15, 15);
printHit(g1, 5, 5);
LibWeb: Reorder paintable hit-testing to account for `pointer-events` Instead of ignoring any paintable immediately when they're invisible to hit-testing, consider every candidate and while the most specific candidate is invisible to hit-testing, traverse up to its parent paintable. This more closely reflects the behavior expected when wrapping block elements inside inline elements, where although the block element might have `pointer-events: none`, it still becomes part of the hit-test body of the inline parent. This makes the following link work as expected: <a href="https://ladybird.org"> <div style="pointer-events: none">Ladybird</div> </a>
2025-01-21 15:24:46 +01:00
});
</script>
Reference in a new issue Copy permalink