Contact emails
fla...@chromium.org, liviu...@chromium.org, xida...@chromium.org
Explainer
https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior
Spec
https://drafts.csswg.org/css-overscroll-1/#propdef-overscroll-behavior
Tracking bug
Summary
The overscroll-behavior CSS property sets what a browser does when reaching the boundary of a scrolling area. It is a shorthand for overscroll-behavior-x and overscroll-behavior-y.
Chrome fully supports this feature since M63. However, there is a known bug that the overscroll-behavior is propagated from body element to the viewport, where the correct behavior is from html to the viewport.
We intend to fix the bug and ship the correct behavior. The current measure shows that this change might cause different behavior on ~2% of web pages. These 2% web pages can be broken down into two cases:
The sites that will now prevent overscroll after the fix. In this case, the developer already wanted to prevent overscroll, so the fix shouldn’t harm their sites.
The sites that will now no longer prevent overscroll after the fix. In this case, a site would have overscroll prevent set in the body, but not in the html. After the fix, the behavior would be consistent with Firefox and Safari (which doesn’t yet implement the overscroll-behavior). Given the incomplete support of overscroll-behavior, it’s unlikely that this will break sites. Moreover, when it does initiate overscroll it does show a UI affordance which lets the users know what is happening.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Demo
Here is a demo that reflects the buggy case.
Risks
Interoperability and Compatibility
Firefox: Full support from M59
Edge: Not fully supported.
Safari: No signal
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
We will ensure that there is test coverage for the buggy case under this test suite.
Entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALRxhAu%3DCDnPDv8nerEr6YvLTeeCM2T0SsxTWP%2B2nbBWKgmQaw%40mail.gmail.com.
From an API owner perspective, the 2% number is in a range where we need to understand more what is affected.
I understand that it's unlikely to cause serious breakage, but if usage could be driven down by changing those sites you are talking about, that would make the decision less risky. Could you return when you have more information about that, and we could continue from there?
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALRxhAtpxWMKfSGESe_jUZ6snevi5ESjSQcrfE%2BPG%2BuyX9Toww%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALRxhAu%3DCDnPDv8nerEr6YvLTeeCM2T0SsxTWP%2B2nbBWKgmQaw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALRxhAu%3DCDnPDv8nerEr6YvLTeeCM2T0SsxTWP%2B2nbBWKgmQaw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.