blob: 0b380574bc5df0731605d14f0adb34cd13e61350 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
<!DOCTYPE html>
<meta charset="UTF-8">
<title>CSS Highlight API Test: Overlapping Highlights</title>
<link rel="help" href="https://drafts.csswg.org/css-highlight-api-1/">
<link rel="match" href="custom-highlight-painting-overlapping-highlights-001-ref.html">
<meta name="assert" value="UAs must not define any styles for custom highlight pseudo-elements in the default UA stylesheet.">
<style>
body {
font-size: 3em;
font-weight: bolder;
}
#affected1::highlight(highlight1) {
color: red;
}
#affected2::highlight(highlight2) {
color: green;
}
</style>
<body><span id="affected1">This should have 'highlight1' style (red).</span><span id="affected2">This should have 'highlight2' style (green).</span>
<script>
/*
This test is meant to verify that:
- UAs must not define any styles for custom highlight pseudo-elements in
the default UA stylesheet.
- UAs do not paint unstyled custom highlights.
In this test, highlight2 has higher priority because it was registered
later, so it is painted over highlight1. This includes painting for
span#affected1, where there is no CSS rule for highlight2. But since unstyled
custom highlights are not painted, span#affected1 is still painted with the
styles for highlight1.
See https://drafts.csswg.org/css-highlight-api-1/#default-styles
*/
const node = document.body;
let r = new Range();
r.setStart(node, 0);
r.setEnd(node, 2);
CSS.highlights.set("highlight1", new Highlight(r));
CSS.highlights.set("highlight2", new Highlight(r));
</script>
|
