Add a WPT which checks that overscroll-behavior is respected on the <html> element
Categories
(Core :: Panning and Zooming, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | fixed |
People
(Reporter: botond, Assigned: emilio)
References
(Regressed 1 open bug)
Details
Attachments
(1 external file)
Chrome has a bug where it does not respect overscroll-behavior on the <html> element, only on the <body>.
To improve interop in this area, I would like to suggest adding a web platform test which checks for respecting overscroll-behavior on <html> specifically.
I think a way such a test could be formulated is to have an <iframe> with overscroll-behavior: contain on its <html> element, and check that scroll chaining from the iframe's contents to the enclosing document is successfully prevented.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
For now I created two manual testcases:
- https://theres-waldo.github.io/mozilla-testcases/overscroll-behavior-contain-iframe-html.html
- https://theres-waldo.github.io/mozilla-testcases/overscroll-behavior-contain-iframe-body.html
The STR for both is:
- Scroll the page down to bring the iframe into view
- Try to scroll the iframe upwards, and see if scroll chaining to scroll the enclosing page upwards works
Comment 2•3 years ago
|
||
Tested on Safari on macos.
Scrolling the iframe up does NOT scroll the page in overscroll-behavior-contain-iframe-html.html
Scrolling the iframe up does scroll the page in overscroll-behavior-contain-iframe-body.html
Comment 3•3 years ago
|
||
I was able to test on Safari an iOS device.
For both testcases, scrolling up the iframe overscrolled the iframe and did not scroll the page.
| Reporter | ||
Comment 4•3 years ago
•
|
||
(In reply to Timothy Nikkel (:tnikkel) from comment #3)
For both testcases, scrolling up the iframe overscrolled the iframe and did not scroll the page.
Huh, that's an interesting discrepancy betweeen macOS and iOS (or perhaps touchpad scrolling vs. touch scrolling).
I'd be curious to know whether the following two pages (which are just the same pages that are contained inside iframes in the previous test cases) allow pull-to-refresh in Safari on iOS:
| Reporter | ||
Comment 5•3 years ago
|
||
I proposed improving interop in this area for Interop 2024: https://github.com/web-platform-tests/interop/issues/560
We discussed the proposal in today's Interop 2024 triage meeting, and it was suggested that, to improve the chances of the proposal being accepted by other browser vendors, we should try to contribute these WPTs as soon as possible.
Emilio kindly offered to try turning the manual testcases from comment 1 into WPTs (needinfoing as requested).
Note that due to bug 1797215, Firefox will likely not pass these WPTs yet (but that's fine, getting them to pass can be part of the work we do during the Interop 2024 process).
| Reporter | ||
Comment 6•3 years ago
|
||
We have this existing WPT for overscroll-behavior, the new tests could be adaptations of this one where instead of a scrollable <div> we have a scrollable subdocument.
| Assignee | ||
Comment 7•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 8•3 years ago
|
||
Does comment 7 look reasonable? Fails on Chrome here as expected.
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
Backed out for causing failures at overscroll-behavior-root.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/372618c6e03d17313a0c5f43d0054babb9e89074
Push where failures started: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=QvxTNKfPTfybWVcUyRoxcg.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=6e5782df6da147ae5c916097b12efcfae7149b5c
Failure log: https://treeherder.mozilla.org/logviewer?job_id=434568361&repo=autoland&lineNumber=2947
Comment 14•3 years ago
|
||
| Assignee | ||
Updated•3 years ago
|
Comment 15•3 years ago
|
||
| bugherder | ||
Description
•