diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-19 00:47:55 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-19 00:47:55 +0000 |
| commit | 26a029d407be480d791972afb5975cf62c9360a6 (patch) | |
| tree | f435a8308119effd964b339f76abb83a57c29483 /layout/reftests/bugs/1743533-1.html | |
| parent | Initial commit. (diff) | |
| download | firefox-26a029d407be480d791972afb5975cf62c9360a6.tar.xz firefox-26a029d407be480d791972afb5975cf62c9360a6.zip | |
Adding upstream version 124.0.1.upstream/124.0.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'layout/reftests/bugs/1743533-1.html')
| -rw-r--r-- | layout/reftests/bugs/1743533-1.html | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/layout/reftests/bugs/1743533-1.html b/layout/reftests/bugs/1743533-1.html new file mode 100644 index 0000000000..9d4764b349 --- /dev/null +++ b/layout/reftests/bugs/1743533-1.html @@ -0,0 +1,35 @@ +<!DOCTYPE html><html class="reftest-paged"> +<style>html{font-size:12pt}</style> +<!-- http example.org uri makes this an oop if with fission --> +<iframe style="height: 1000vh" src="http://example.org/1743533-1-helper.html"></iframe> +</html> + +<!-- +Some notes about this test. +To reproduce the problem we just need an oop iframe that spans multiple pages, +and some content in it that also spans multiple pages. I used text instead +of a background color because background colors don't show up by default in +print preview. We're using page mode here and not print preview, so that is +not technically required here. + +We'd like to compare an oop iframe and an in process iframe with the same +content to make sure they are the same. But some idiosyncracies with scrollbars +in paged mode cause the rendering not to be exactly the same. Since paged mode +is just for testing, and printing doesn't have scrollbars, it doesn't seem +worth digging too much into it. + +We compare an iframe with content in it, to a blank iframe, and then we use a +high minimum accepted number of pixels differing in the fuzz. This then makes +sure the two documents differ by enough pixels. + +Note why we couldn't use other test types: + +I tried to write this as a wpt print reftest, it did not reproduce the bug. +I'm not sure what wpt reftests use to simulate printing, but I suspect it +is not similar enough to our print preview to trigger the bug. + +I tried to add this as a test to layout/base/tests/chrome/test_printpreview.xhtml +but that is not feasible because that test runs as part of the mochitest-chrome +suite, which I'm told doesn't even run in e10s mode, and definitely does not get +run with fission, which is required to reproduce the bug. +--> |