File: http-equiv-and-name-1.html

package info (click to toggle)
thunderbird 1%3A140.5.0esr-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 4,609,180 kB
  • sloc: cpp: 7,672,739; javascript: 5,901,898; ansic: 3,898,899; python: 1,413,347; xml: 653,997; asm: 462,284; java: 180,927; sh: 113,491; makefile: 20,463; 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 (23 lines) | stat: -rw-r--r-- 1,154 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
22
23
 
<!doctype html>
<title>Setting both http-equiv and name attributes on a meta element</title>
<meta http-equiv=content-language name=color-scheme content=dark>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="color-scheme/support/compute-root-color-scheme.js"></script>
<!--
  NOTE: This test assumes that the browser's default color-scheme is "light",
  see https://github.com/web-platform-tests/wpt/pull/31268 for reasoning
-->
<script>
  // This creates a test()
  assert_root_color_scheme("dark", "<meta> set the color-scheme to dark");

  // We can't test content-language against :lang(), because CSS Selectors 4
  // references BCP 47 syntax and RFC4647 "Matching of Language Tags", but
  // "dark" is not a well-formed BCP 47 tag and therefore cannot be matched.
  // Therefore, the test that content-language gets set is split off to a
  // separate testcase using a well-formed lang tag as the content.
  // test(() => {
  //   assert_equals(document.querySelector(":root:lang(dark)"), document.documentElement);
  // }, "<meta> set the content-language to dark");
</script>