LGTM1 On Tue, Sep 22, 2026 at 9:13 AM Chromestatus < [email protected]> wrote:
> *Contact emails* > [email protected] > > *Explainer* > https://github.com/explainers-by-googlers/scroll-snap-type-pair > > *Specification* > https://drafts.csswg.org/css-scroll-snap-1 > > *Summary* > https://github.com/w3c/csswg-drafts/issues/9519 Add a "pair" keyword to > scroll-snap-type. If used, when the container scroll snaps to an element on > one axis, it should snap to the same element on the other axis. In the > existing spec, the "both" keyword allows the scroll container to select > snap targets in X and Y axes independently and snap to different targets. > > *Blink component* > Blink>Scroll > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EScroll%22> > > *Web Feature ID* > scroll-snap <https://webstatus.dev/features/scroll-snap> > > *Motivation* > See explainer > > *Initial public proposal* > https://github.com/w3c/csswg-drafts/issues/9519 > > *TAG review* > https://github.com/w3ctag/design-reviews/issues/1271 > > *TAG review status* > Pending > > *Goals for experimentation* > None > > *Risks* > > > *Interoperability and Compatibility* > No risk because this is a new feature. > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/1448) > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/716) > > *Web developers*: No signals > > *Other signals*: > > *WebView application risks* > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > No risks > > > *Debuggability* > *No information provided* > > *Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)?* > Yes > > *Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* > Yes > > https://wpt.fyi/results/?label=master&label=experimental&aligned&q=scroll-snap-type-pair > > *Flag name on about://flags* > *No information provided* > > *Finch feature name* > CSSScrollSnapTypePair > > *Rollout plan* > Will ship enabled for all users > > *Requires code in //chrome?* > False > > *Tracking bug* > https://crbug.com/542706103 > > *Estimated milestones* > Shipping on desktop 156 > Shipping on Android 156 > Shipping on WebView 156 > > *Anticipated spec changes* > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > *No information provided* > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5124378896498688?gate=6676576856047616 > > *Links to previous Intent discussions* > Intent to Prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a8754d6.0a50a06e.201ba6.08b5.GAE%40google.com > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.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 [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6ab2a927.2685d652.5e210.0041.GAE%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6ab2a927.2685d652.5e210.0041.GAE%40google.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8qRsH11AP9Ya4Cphb0nMy749E14JOpz6buAREYBOe%3DAA%40mail.gmail.com.
