diff options
Diffstat (limited to 'testing/web-platform/tests/css/printing/fragmented-inline-block-002-print.html')
| -rw-r--r-- | testing/web-platform/tests/css/printing/fragmented-inline-block-002-print.html | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/testing/web-platform/tests/css/printing/fragmented-inline-block-002-print.html b/testing/web-platform/tests/css/printing/fragmented-inline-block-002-print.html new file mode 100644 index 0000000000..c5390aad6c --- /dev/null +++ b/testing/web-platform/tests/css/printing/fragmented-inline-block-002-print.html @@ -0,0 +1,25 @@ +<!DOCTYPE html> +<html> +<head> + <meta charset="utf-8"> + <title>test that inline-blocks are fragmented in print output</title> + <link rel="help" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1740304"> + <link rel="match" href="fragmented-inline-block-002-print-ref.html"> + <style> + .tall { + /* The reference case has a block; we have an inline-block. + Given that there's no other content on our line, we can expect our + inline-block to end up rendering and fragmenting like the + reference case's block. */ + display: inline-block; + + height: 10in; + width: 1in; + border: 0.5in solid black; + } + </style> +</head> +<body> + <div class="tall"></div> +</body> +</html> |