I'm excited to see this ship! On Fri, Feb 14, 2025 at 1:57 PM 'Ajay Rahatekar' via blink-dev < blink-dev@chromium.org> wrote:
> Contact emails > > fla...@chromium.org, sakha...@chromium.org > > Summary > > This is a combined Intent to ship for the following features: > > ::scroll-marker and ::scroll-marker-group for scrolling containers: > > Pseudo elements that allow to create a set of focusable markers for all of > the associated items within the scrolling container. > > ::scroll-button(<direction>): > > Focusable pseudo-element button that allows scrolling the scrolling > container in the associated direction. > > ::column > > Supports associating ::scroll-marker elements with column fragments and > scroll snap aligning to columns. > > Explainer > > https://chrome.dev/carousel/ > > > https://github.com/w3c/csswg-drafts/blob/main/css-overflow-5/carousel-explainer.md > > Specification > > https://drafts.csswg.org/css-overflow-5/#scroll-navigation > > https://drafts.csswg.org/css-multicol-2/#column-pseudo > > Blink component > > Blink>CSS > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> > > TAG review > > https://github.com/w3ctag/design-reviews/issues/1037 > > TAG review status > > Pending > > Risks > > Interoperability and Compatibility > > None > > > Gecko: https://github.com/mozilla/standards-positions/issues/1161 > > WebKit: https://github.com/WebKit/standards-positions/issues/447 > > Web developers: Positive > > - > > https://x.com/f3rg_codes/status/1889283883910472004 > - > > > > https://www.youtube.com/watch?v=rE-qmyPHHGw&t=1s#:~:text=those%20carousel%20examples%20are%20wild!%20holy%20smokes%20 > - > > > > https://utilitybend.com/blog/love-at-first-slide-creating-a-carousel-purely-out-of-css > > > > 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? > > None > > > Debuggability > > Basic DevTools support is expected to be available when the features ship. > Extended support for debugging is under investigation > > > 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 > > css/css-overflow/{column*, scroll-button*, scroll-marker*} > > Flag name on about://flags > > None > > Finch feature name > > CSSPseudoScrollButtons, CSSPseudoScrollMarkers, CSSPseudoColumn > > Non-finch justification > > None > > Requires code in //chrome? > > False > > Tracking bug > > https://issues.chromium.org/issues/332396355 > > https://issues.chromium.org/issues/358119263 > > https://issues.chromium.org/issues/365680822 > > Estimated milestones > > 135 > > > 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). > > None > I see a number of open issues on GitHub <https://github.com/w3c/csswg-drafts/labels/css-overflow-5>, at least one <https://github.com/w3c/csswg-drafts/issues/10935> or two <https://github.com/w3c/csswg-drafts/issues/10918> of which sound like they would have web compat implications. Can you do a triage pass over the open issues and summarize here what you see the web compat risk to be for potentially upcoming spec changes to resolve the issues? Given this is an unpolyfillable CSS feature I assume we don't expect much adoption until there's multi-engine support and so are likely to be able to make breaking changes for a while after we ship if necessary, right? > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5160035463462912 > <https://chromestatus.com/feature/5160035463462912?gate=5195983131770880> > > https://chromestatus.com/feature/5192332683771904 > > https://chromestatus.com/feature/5093129273999360 > > Links to previous Intent discussions > > Intent to Prototype: > > https://groups.google.com/a/chromium.org/g/blink-dev/c/4hDfC6nBoP0 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/4hDfC6nBoP0/m/9XF2RbLtAAAJ> > > https://groups.google.com/a/chromium.org/g/blink-dev/c/hoBT5TPKRrw > > https://groups.google.com/a/chromium.org/g/blink-dev/c/ZPXC1I9E1Vw > > 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 blink-dev+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAg57vSk1VeA-yi8HmM5XV%3D0fKba2kJQFOkwoC13kDL4mg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAg57vSk1VeA-yi8HmM5XV%3D0fKba2kJQFOkwoC13kDL4mg%40mail.gmail.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 blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9Z8MtDXvRyGqtpAcHx0raun8WkxGX9yeSFHRiGCa6a6A%40mail.gmail.com.
