File: min-max-content-orthogonal-flow-crash-001.html

package info (click to toggle)
thunderbird 1%3A140.3.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 4,608,620 kB
  • sloc: cpp: 7,671,641; javascript: 5,901,032; ansic: 3,899,013; python: 1,413,270; xml: 653,997; asm: 462,284; java: 180,948; sh: 113,489; makefile: 20,460; perl: 14,288; objc: 13,059; yacc: 4,583; pascal: 3,352; lex: 1,720; ruby: 1,222; exp: 762; sql: 715; awk: 580; php: 436; lisp: 430; sed: 70; csh: 10
file content (30 lines) | stat: -rw-r--r-- 712 bytes parent folder | download | duplicates (22) 
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
 
<!DOCTYPE html>
<title>CSS Test: Check computing min-/max-content does not cause crash</title>
<link rel="help" href="https://crbug.com/976859">
<link rel="help" href="https://drafts.csswg.org/css-sizing-3/#sizing-values">
<link rel="author" title="Koji Ishii" href="mailto:kojii@chromium.org">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<style>
body {
  width: fit-content;
}
#target {
  display: block;
  writing-mode: vertical-lr;
  columns: 2;
}
.after #target {
  float: left;
}
</style>
<body>
  <div id="target"></div>
<script>
test(() => {
  const body = document.body;
  body.offsetTop;
  body.classList.add("after");
});
</script>
</body>