tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

monolithic-overflow-032-print.tentative.html (1269B)


      1 <!DOCTYPE html>
      2 <link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
      3 <link rel="help" href="https://issues.chromium.org/40415661">
      4 <link rel="match" href="monolithic-overflow-032-print-ref.html">
      5 <style>
      6  :root {
      7    print-color-adjust: exact;
      8  }
      9  body {
     10    margin: 0;
     11  }
     12  @page {
     13    size: 400px 300px;
     14    margin: 0;
     15  }
     16 </style>
     17 <!-- It's not obvious that the expected behavior here is correct, but Blink and
     18     Gecko agree on it. Essentially, we expect that when the tall monolithic
     19     content has been fully placed (see the third page), and there's more
     20     content after it, a new fragment starts right after the fragment with tall
     21     monolithic content. This means that it would appear that there are two
     22     fragments from the same node on the same page, but this is not really the
     23     case, since the first fragment is just a huge fragment that has run all the
     24     way since the first page. -->
     25 <div style="box-decoration-break:clone; height:1800px; border:solid black; border-width:10px 0; border-bottom-color:gray;">
     26  <div style="contain:size; width:50%; box-sizing:border-box; border:solid hotpink; height:850px; background:yellow;"></div>
     27  <div style="width:25%; height:300px; background:cyan;"></div>
     28 </div>