Content - a09538689d88fec2b9c6337664142255f8083ddc - 18ae17e/css/css-gcpm/string-set-011.html

visit type:

Tip revision: 4f06a45252465792447f80b6559b17c4c4e9712c authored by Daniel Vogelheim on 10 April 2018, 13:07:39 UTC
Implement deprecation of content type sniffing for workers.

Tip revision: 4f06a45

string-set-011.html

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>CSS Test: GCPM string-set on element with display: none</title>
<link rel="author" title="Dave Cramer" href="mailto:dauwhe@gmail.com">
<link rel="help" href="http://www.w3.org/TR/css-gcpm-3/#setting-named-strings-the-string-set-pro">
<meta name="flags" content="paged">
<meta name="assert" content="Test checks that a string can be set to the value of an element even if display is set to none">
<!--
Note this test exposes a known bug in PrinceXML 9.0 rev 2 (and all previous versions)
-->
<style>
  @page {
   @top-center {
   content: string(title);
   }
  }

 h1 {
 string-set: title content();
 display: none;
 }

#d2 { page-break-before: always; }

</style>
</head>
<body>
<h1>Chapter One Title</h1>
<p>Note: test has two pages</p>
<p>Test passes if:</p>
<ol>
<li>
“Chapter One Title” appears in the running head on page one.
</li>
<li>
“Chapter Two Title” appears in the running head on page two.
</li>
</ol>

<div id="d2">
<h1>Chapter Two Title</h1>
<p>Second Page</p>
</div>
</body>
</html>

Browse the archive

https://github.com/web-platform-tests/wpt