diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-28 14:29:10 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-28 14:29:10 +0000 |
| commit | 2aa4a82499d4becd2284cdb482213d541b8804dd (patch) | |
| tree | b80bf8bf13c3766139fbacc530efd0dd9d54394c /layout/reftests/bugs/1081072-1.html | |
| parent | Initial commit. (diff) | |
| download | firefox-upstream.tar.xz firefox-upstream.zip | |
Adding upstream version 86.0.1.upstream/86.0.1upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'layout/reftests/bugs/1081072-1.html')
| -rw-r--r-- | layout/reftests/bugs/1081072-1.html | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/layout/reftests/bugs/1081072-1.html b/layout/reftests/bugs/1081072-1.html new file mode 100644 index 0000000000..59b1a83549 --- /dev/null +++ b/layout/reftests/bugs/1081072-1.html @@ -0,0 +1,44 @@ +<!DOCTYPE html> +<html class="reftest-wait"> +<head> + <!-- NOTE: This bug was triggered by scrollbar opacity-fading, so this + testcase needs to be loaded with this pref... + layout.testing.overlay-scrollbars.always-visible + ...set to *false* in order to have a chance to trigger the bug. + + We don't have to worry about this producing any screenshots of + unpredictable partially-faded-scrollbars in our reftest snapshot, + because our scrollbars don't actually paint here, since the + scrollable element has "overflow:auto" and doesn't overflow + (because it's auto-sized to fit its content). --> + <style> + .container { + display: flex; + overflow-y: auto; + border: 1px solid black; + } + </style> + <script type='text/javascript'> + window.addEventListener("MozReftestInvalidate", startTest); + + function startTest() { + // NOTE: setTimeout in tests is evil, but it's necessary here -- we need + // to wait until the scrollbars have finished fading, and there's no + // event we can listen for to signal that, AFAIK. Fortunately, there + // shouldn't be *visible* scrollbars in this testcase, so even if our + // setTimeout fires too early/late, the test will still pass. (So, there + // shouldn't be spurious failures; any failures that happen will be real.) + setTimeout(endTest, 800); + } + + function endTest() { + document.documentElement.removeAttribute("class"); + } + </script> +</head> +<body> + <div class="container"> + <div>T</div> + </div> +</body> +</html> |