LGTM3 On Mon, Jun 22, 2026 at 11:40 AM Alex Russell <[email protected]> wrote:
> LGTM2 > > On Friday, June 19, 2026 at 11:01:45 AM UTC-7 Rick Byers wrote: > >> No problem, thank you Mustaq! >> >> On Fri, Jun 19, 2026 at 12:37 PM Mustaq Ahmed <[email protected]> >> wrote: >> >>> Thanks Rick! >>> >>> I requested a web feature ID at web-features/issues/4100 >>> <https://github.com/web-platform-dx/web-features/issues/4100> already. >>> I thought I added the link somewhere on the Chromestatus page, sorry! >>> >>> >>> On Fri, Jun 19, 2026 at 12:29 PM Rick Byers <[email protected]> wrote: >>> >>>> Chromestatus warned me there is no response to the web feature >>>> question. Reading the guidance >>>> <https://github.com/web-platform-dx/web-features/blob/main/docs/CONTRIBUTING.md#hints-for-distinguishing-features>, >>>> I think probably you should request a new web feature ID for this, WDYT? >>>> >>>> >>>> On Fri, Jun 19, 2026 at 12:25 PM Rick Byers <[email protected]> >>>> wrote: >>>> >>>>> Great, LGTM1 >>>>> >>>>> On Thu, Jun 18, 2026 at 4:59 PM Mustaq Ahmed <[email protected]> >>>>> wrote: >>>>> >>>>>> On Wed, Jun 17, 2026 at 11:23 AM Rick Byers <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Happy to see this ship (after apparently dropping the ball on it >>>>>>> myself >>>>>>> <https://github.com/w3c/pointerevents/issues/587#issuecomment-3740724369> >>>>>>> over a decade ago)! >>>>>>> >>>>>>> Shouldn't there at least be a WPT for the existence of the >>>>>>> `momentum` (i.e. in the IDL tests for WheelEvent)? >>>>>>> >>>>>> >>>>>> Yes, we have a test already for idl coverage, thanks for the catch! I >>>>>> updated the chromestatus entry to mention this: >>>>>> pointerevents/idlharness.https.window.html >>>>>> <https://wpt.fyi/results/pointerevents/idlharness.https.window.html?label=experimental&label=master&aligned> >>>>>> (see >>>>>> "attribute momentum"). >>>>>> >>>>>> Ideally there'd also be a test that verifies the bool gets plumbed >>>>>>> through, i,.e. by extending webdriver wheel actions. Might web >>>>>>> developers >>>>>>> need that for proper automated testing of these advanced scrolling UX? >>>>>>> Can >>>>>>> you at least file a bug to track the missing automation here? I'm OK not >>>>>>> blocking shipping on that if you prefer. >>>>>>> >>>>>> >>>>>> I filed this feature request for TestDriver: >>>>>> web-platform-tests/wpt/issues/60724 >>>>>> <https://github.com/web-platform-tests/wpt/issues/60724> >>>>>> >>>>>> >>>>>>> Rick >>>>>>> >>>>>>> On Wed, Jun 17, 2026 at 11:17 AM Yoav Weiss (@Shopify) < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Is it possible to share an explainer (even an inline one) RE the >>>>>>>> use cases for this and how we expect developers to use this? >>>>>>>> >>>>>>> >>>>>> A custom scroll curve that decays faster during the momentum phase >>>>>> comes to mind. I believe we can review web developers' comments about >>>>>> it to find more use cases (for context, this feature appears in the >>>>>> top third of the spec-reactions >>>>>> <https://foolip.github.io/spec-reactions/#:~:text=w3c/pointerevents%23587> >>>>>> dashboard). Unfortunately, I'll need some time before I can >>>>>> complete a useful demo. >>>>>> >>>>>> >>>>>>> >>>>>>>> On Tuesday, June 16, 2026 at 9:56:47 PM UTC+2 Mustaq Ahmed wrote: >>>>>>>> >>>>>>>>> On Tue, Jun 16, 2026 at 3:32 PM Mike Taylor < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 6/16/26 11:21 a.m., Chromestatus wrote: >>>>>>>>>> >>>>>>>>>> *Contact emails* >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>>> *Specification* >>>>>>>>>> https://w3c.github.io/pointerevents/#dom-wheelevent-momentum >>>>>>>>>> >>>>>>>>>> *Summary* >>>>>>>>>> The wheel events on many native platforms simulate scrolling >>>>>>>>>> inertia: the events continue to fire for a while after the user has >>>>>>>>>> lifted >>>>>>>>>> the finger from the trackpad after a fling interaction. This feature >>>>>>>>>> exposes a momentum attribute in wheel events which is true only for >>>>>>>>>> those >>>>>>>>>> simulated events, differentiating them from the events fired during >>>>>>>>>> the >>>>>>>>>> physical scroll interaction. This lets web developers ignore fling >>>>>>>>>> events >>>>>>>>>> or customize rich fling effects. >>>>>>>>>> >>>>>>>>>> *Blink component* >>>>>>>>>> Blink>Input >>>>>>>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EInput%22> >>>>>>>>>> >>>>>>>>>> *Web Feature ID* >>>>>>>>>> Missing feature >>>>>>>>>> >>>>>>>>>> *Motivation* >>>>>>>>>> *No information provided* >>>>>>>>>> >>>>>>>>>> *Initial public proposal* >>>>>>>>>> *No information provided* >>>>>>>>>> >>>>>>>>>> *TAG review* >>>>>>>>>> This feature is too small and non-controversial to justify a TAG >>>>>>>>>> review. >>>>>>>>>> >>>>>>>>>> *TAG review status* >>>>>>>>>> Not applicable >>>>>>>>>> >>>>>>>>>> *Goals for experimentation* >>>>>>>>>> None >>>>>>>>>> >>>>>>>>>> *Risks* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Interoperability and Compatibility* >>>>>>>>>> *No information provided* >>>>>>>>>> >>>>>>>>>> *Gecko*: Positive ( >>>>>>>>>> https://lists.w3.org/Archives/Public/public-pointer-events/2026JanMar/0148.html#:~:text=smaug%3A%20just%20having%20a%20flag%20should%20be%20easy.%20we%27ll%20just%20have%20to%20do%20%0Asomething%20on%20linux) >>>>>>>>>> Supported >>>>>>>>>> the feature during PEWG meeting on 2026-03-11. >>>>>>>>>> >>>>>>>>>> *WebKit*: No signal >>>>>>>>>> >>>>>>>>>> Can we file real vendor position issues for Gecko and WebKit >>>>>>>>>> (but, nice to see the comments from Olli)? >>>>>>>>>> >>>>>>>>> >>>>>>>>> Filed standard position requests: >>>>>>>>> https://github.com/mozilla/standards-positions/issues/1425 and >>>>>>>>> https://github.com/WebKit/standards-positions/issues/688 >>>>>>>>> >>>>>>>>> >>>>>>>>>> *Web developers*: Positive ( >>>>>>>>>> https://github.com/w3c/pointerevents/issues/587) See the dev >>>>>>>>>> discussion and also many thumbs-up emojis. >>>>>>>>>> >>>>>>>>>> *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 information provided* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Debuggability* >>>>>>>>>> *No information provided* >>>>>>>>>> >>>>>>>>>> *Will this feature be supported on all six Blink platforms >>>>>>>>>> (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?* >>>>>>>>>> No >>>>>>>>>> >>>>>>>>>> *Is this feature fully tested by web-platform-tests >>>>>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >>>>>>>>>> No >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Flag name on about://flags* >>>>>>>>>> *No information provided* >>>>>>>>>> >>>>>>>>>> *Finch feature name* >>>>>>>>>> WheelEventMomentum >>>>>>>>>> >>>>>>>>>> *Rollout plan* >>>>>>>>>> Will ship enabled for all users >>>>>>>>>> >>>>>>>>>> *Requires code in //chrome?* >>>>>>>>>> False >>>>>>>>>> >>>>>>>>>> *Tracking bug* >>>>>>>>>> https://crbug.com/40704952 >>>>>>>>>> >>>>>>>>>> *Estimated milestones* >>>>>>>>>> Shipping on desktop 151 >>>>>>>>>> Shipping on Android 151 >>>>>>>>>> Shipping on WebView 151 >>>>>>>>>> >>>>>>>>>> *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/6631012282007552?gate=5864164607262720 >>>>>>>>>> >>>>>>>>>> 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/6a3169e4.9a65a9ce.314fea.0299.GAE%40google.com >>>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a3169e4.9a65a9ce.314fea.0299.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/9807a897-2c36-4ce5-8e1e-244f92f33139n%40chromium.org >>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9807a897-2c36-4ce5-8e1e-244f92f33139n%40chromium.org?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/235a04f5-03e8-471c-8c3f-cb72d4aa1e33n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/235a04f5-03e8-471c-8c3f-cb72d4aa1e33n%40chromium.org?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/CAOMQ%2Bw-UK1HL_wPCU6DNfXKQSSJ0wO%3D3B41Nt8QS4dKvO8469Q%40mail.gmail.com.
