File: custom-highlight-painting-016.html

package info (click to toggle)
thunderbird 1%3A143.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 4,703,968 kB
  • sloc: cpp: 7,770,492; javascript: 5,943,842; ansic: 3,918,754; python: 1,418,263; xml: 653,354; asm: 474,045; java: 183,079; sh: 111,238; makefile: 20,410; perl: 14,359; objc: 13,059; yacc: 4,583; pascal: 3,405; lex: 1,720; ruby: 999; exp: 762; sql: 715; awk: 580; php: 436; lisp: 430; sed: 69; csh: 10
file content (21 lines) | stat: -rw-r--r-- 906 bytes parent folder | download | duplicates (18) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
 
<!DOCTYPE html>
<meta charset="UTF-8">
<title>CSS Highlight API Test: Painting</title>
<link rel="help" href="https://drafts.csswg.org/css-highlight-api-1/">
<link rel="match" href="custom-highlight-painting-001-ref.html">
<meta name="assert" value="Highlighted elements must be correctly painted and there should be no caching that doesn't take highlight names into account">
<style>
  #affected::highlight(foo) {
    background-color: yellow;
    color: blue;
  }
</style>
<body><span></span><span id="affected">One </span><span id="affected">two </span><span>three…</span>
<script>
  // The first <span> style resolution shouldn't cause caching an empty set of matched properties that could be used with the spans that should be highlighted later.
  const node = document.body;
  let r = new Range();
  r.setStart(node, 1);
  r.setEnd(node, 3);
  CSS.highlights.set("foo", new Highlight(r));
</script>