overscroll-behavior on the root scroller #560
Comments
|
@theres-waldo are the tests you're contributing in https://bugzilla.mozilla.org/show_bug.cgi?id=1857130 necessarily manual, or could they be automated? We have no infrastructure to run manual tests and include them in Interop 202X scores, unfortunately. |
I believe they can be automated, we just haven't had a chance to create automated versions yet. |
|
A WPT for this is now written: https://wpt.fyi/results/css/css-overscroll-behavior/overscroll-behavior-root.html |
|
Also, to note, this is the only overscroll-behavior test not in the existing scrolling focus area: https://wpt.fyi/results/css/css-overscroll-behavior?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&q=not%20label%3Ainterop-2022-scrolling%20path%3A%2Fcss%2Fcss-overscroll-behavior. (See also: #471.) |
We can think of the changes that Blink would need to make to align with the current spec as having wo parts:
Would it be fair to say that (1) is a less risky change than (2)? I think, from a web compat point of view, we mostly care about (1). Would it help increase consensus on this issue to explicitly reduce the scope to just (1)? (The WPT already only tests (1), but I can see the issue's scope being ambiguous from the description.) |
|
Thank you for proposing overscroll-behavior on the root scroller for inclusion in Interop 2024. We wanted to let you know that this proposal was not selected to be part of Interop 2024. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year, if necessary. For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024! Posted on behalf of the Interop team. |
Description
There is implementation divergence on whether overscroll-behavior on the root scroller needs to be specified on the
<html>element or the<body>element.Gecko only respects it on the
<html>element.Blink only respects it on the
<body>element (Chromium issue).Webkit behaviour to be investigated.
Based on this example in the spec, and this comment in the Chromium issue, I believe the Gecko behaviour is the correct one.
I'm not aware of a Web Platform Test currently exercising this but I think one could be added and I filed a Gecko issue to contribute one.
Specification
https://drafts.csswg.org/css-overscroll/
Open Issues
No response
Tests
https://bugzilla.mozilla.org/show_bug.cgi?id=1857130
https://wpt.fyi/results/css/css-overscroll-behavior/overscroll-behavior-root.html
Current Implementations
Standards Positions
No response
Browser bug reports
https://bugs.chromium.org/p/chromium/issues/detail?id=954423
Developer discussions
No response
Polls & Surveys
No response
Existing Usage
No response
Workarounds
No response
Accessibility Impact
No response
Privacy Impact
No response
Other
No response
The text was updated successfully, but these errors were encountered: