-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Carryover evaluation: Scrolling #471
Comments
We should consider the overlap between this and #492 filed by @johannesodland. There are a lot of unlabeled tests for scroll snap to consider. |
I strongly recommend that scrolling be carried over. There are still plenty of interoperability issues in this area. To point to a few in WebKit: Body scrolling which cannot be reliably prevented (mentioned before interop 2023):
Issues with CSS pointer-events:
Other issues related to touch/pointer events, overscroll and scroll-snap: |
We reviewed the full list of failing tests in css-scroll-snap and identified a high-impact subset to focus on for Scrolling Interop 2024. That subset falls broadly into two groups. Honoring scroll-snap-align for non-input scrolls
Nested and scrollport-covering snap areas
In the first group, scroll-target-snap-* is also in scope for Interop 2023 and the Chrome fix is tracked by crbug.com/1325845. The scroll-target-align-* tests expect scroll-snap-align to be honored even inside scroll-snap-type:none, which is called out as optional behavior in the spec. However we should adopt this behavior if we plan to introduce scroll-align as an equivalent. The second group consists mainly of changes that Chrome has recently made to its handling of covering and nested snap areas, described in the blink-dev PSA and links therein. There is an open issue to provide greater spec clarity here. |
This came to our attention recently and probably belongs here as well. |
Here's a wpt.fyi view of the proposed test expansion in #471 (comment): |
To evaluate continuation of the Scrolling focus area in Interop 2024
Original proposal:
Labeled tests (2023):
Also consider the possibility of adding new tests in 2024
The text was updated successfully, but these errors were encountered: