Scroll drag with mouse is being discussed in https://github.com/w3c/pointerevents/issues/512 with a potential API for it.
On Wed, Feb 12, 2025 at 11:13 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM3 > > On Wednesday, February 12, 2025 at 5:13:29 PM UTC+1 Alex Russell wrote: > >> Sorry for missing the link to the TAG review. LGTM2, but would love an >> update on scroll drag in some other channel. >> >> Best, >> >> Alex >> >> On Wednesday, February 12, 2025 at 8:10:35 AM UTC-8 Alex Russell wrote: >> >>> Is there a link to the pending TAG review? >>> >>> Also, it's great to see inertness being added, but is there also a >>> solution to click-grab dragging? This is notably missing from native >>> carousel support on the web and I would have expected it to be proposed >>> along with this; e.g. an extension that mirrors `touch-action: pan-x` but >>> for mice. >>> >>> Best, >>> >>> Alex >>> >>> On Wednesday, February 12, 2025 at 7:39:51 AM UTC-8 Rick Byers wrote: >>> >>>> LGTM1 >>>> >>>> On Fri, Feb 7, 2025 at 5:28 PM 'Ajay Rahatekar' via blink-dev < >>>> blink-dev@chromium.org> wrote: >>>> >>>>> Contact emails >>>>> >>>>> fla...@chromium.org, futh...@chromium.org >>>>> >>>>> Explainer >>>>> >>>>> https://github.com/flackr/carousel/tree/main/inert >>>>> >>>>> Specification >>>>> >>>>> https://drafts.csswg.org/css-ui-4/#inertness >>>>> >>>>> https://github.com/whatwg/html/pull/10956 >>>>> >>>>> Summary >>>>> >>>>> The interactivity property specifies whether an element and its flat >>>>> tree descendants (including text runs) are inert or not. >>>>> >>>>> Making an element inert affects whether it can be focused, edited, >>>>> selected, and searchable by find-in-page. It also affects whether it is >>>>> visible in the accessibility tree. >>>>> >>>>> The syntax is: interactivity: auto | inert >>>>> >>>>> >>>>> 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 >>>>> >>>>> 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? >>>>> >>>>> None >>>>> >>>>> >>>>> Debuggability >>>>> >>>>> For the interactivity property, it is debuggable like any other >>>>> keyword property in the styles related panes. >>>>> >>>>> The accessibility tree pane changes the inertness reason from "Inert >>>>> element" and "Inert subtree" to only using "Inert element", where "Inert >>>>> element" now means an element with interactivity computed to inert. >>>>> >>>>> The reason is that the HTML inert attribute is now setting inertness >>>>> through a UA rule for interactivity and can be escaped using the >>>>> interactivity property, whereas previously an inert attribute would force >>>>> a >>>>> whole subtree inert. >>>>> >>>>> >>>>> 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 >>>>> >>>>> - >>>>> >>>>> interactivity-inert-click-002.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-click-002.html> >>>>> - >>>>> >>>>> interactivity-inert-click.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-click.html> >>>>> - >>>>> >>>>> interactivity-inert-find.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-find.html> >>>>> - >>>>> >>>>> interactivity-inert-focus.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-focus.html> >>>>> - >>>>> >>>>> interactivity-inert-fullscreen-ua.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-fullscreen-ua.html> >>>>> - >>>>> >>>>> interactivity-inert-html-attribute-ua.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-html-attribute-ua.html> >>>>> - >>>>> >>>>> interactivity-inert-modal-dialog-ua.html >>>>> <http://wpt.live/css/css-ui/interactivity-inert-modal-dialog-ua.html> >>>>> - >>>>> >>>>> interactivity-computed.html >>>>> <http://wpt.live/css/css-ui/parsing/interactivity-computed.html> >>>>> - >>>>> >>>>> interactivity.html >>>>> <http://wpt.live/css/css-ui/parsing/interactivity.html> >>>>> >>>>> >>>>> Flag name on about://flags >>>>> >>>>> #experimental-web-platform-features >>>>> >>>>> Finch feature name >>>>> >>>>> CSSInert >>>>> >>>>> Non-finch justification >>>>> >>>>> None >>>>> >>>>> Requires code in //chrome? >>>>> >>>>> False >>>>> >>>>> 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 >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> >>>>> https://chromestatus.com/feature/5107436833472512?gate=5112515414196224 >>>>> >>>>> Links to previous Intent discussions >>>>> >>>>> Intent to Prototype: >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/Xuo6HpkN1xQ >>>>> >>>>> >>>>> 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%2BDAjXdDs6n0pUK-8F%2BOyQNUoaesusgVSag%3DSp1NnyYhuxsQ%40mail.gmail.com >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAjXdDs6n0pUK-8F%2BOyQNUoaesusgVSag%3DSp1NnyYhuxsQ%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/CAJh39TN9_vv9WR5DFP_a_DDTwX1Z1JVHzjeUi8iNPwfKjZ0Hog%40mail.gmail.com.
