File: white-space-vs-joiners-001.html

package info (click to toggle)
thunderbird 1%3A144.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 4,725,312 kB
  • sloc: cpp: 7,869,225; javascript: 5,974,276; ansic: 3,946,747; python: 1,421,062; xml: 654,642; asm: 474,045; java: 183,117; sh: 110,973; makefile: 20,398; perl: 14,362; objc: 13,086; yacc: 4,583; pascal: 3,448; lex: 1,720; ruby: 999; exp: 762; sql: 731; awk: 580; php: 436; lisp: 430; sed: 69; csh: 10
file content (37 lines) | stat: -rw-r--r-- 1,158 bytes parent folder | download | duplicates (21) 
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
 
<!DOCTYPE html>
<meta charset=utf-8>

<title>CSS Text Test: join controls do not disrupt white-space processing</title>
<link rel="author" title="Jonathan Kew" href="mailto:jkew@mozilla.com">
<link rel="help" href="https://drafts.csswg.org/css-text-3/#white-space-rules">
<!-- NB: The spec doesn't explicitly discuss join controls in this context,
     but it is self-evident that they should not have any effect on the white-space processing.
     Their only effect should be on the shaping (if any) of the adjacent characters. -->
<link rel="match" href="reference/white-space-vs-joiners-001-ref.html">
<meta name="assert" content="The presence of join controls (ZWJ/ZWNJ) at word edges should not affect white-space processing">

<style>
p {
  width: fit-content;
  border: 2px solid green;
  font: 24px monospace;
}
</style>

<body>
</body>

<script>
for (i = 0x200b; i <= 0x200f; ++i) {
  txt = "  "
    + String.fromCharCode(i)
    + "This should have no leading or trailing ["
    + i.toString(16)
    + "]"
    + String.fromCharCode(i)
    + "  ";
  p = document.createElement("p");
  p.textContent = txt;
  document.body.appendChild(p);
}
</script>