Thanks everyone, we are now landing this to M142. FYI, I wanted to call out the two part shipping plan for this (in case the "Non-finch justification" in the original post was not obvious): - The IDL change for the global event listeners cannot be flag-guarded, so we will ship this part w/o a flag. - The remaining (event firing) part will be shipped by slipping the flag PointerRawUpdateOnlyInSecureContext.
On Mon, Sep 15, 2025 at 2:44 PM Chris Harrelson <[email protected]> wrote: > LGTM3 > > On Mon, Sep 15, 2025 at 11:15 AM 'Dan Clark' via blink-dev < > [email protected]> wrote: > >> LGTM2 >> >> On Monday, September 15, 2025 at 11:00:54 AM UTC-7 [email protected] >> wrote: >> >>> LGTM1 >>> >>> On Monday, September 15, 2025 at 7:33:38 AM UTC-7 Chromestatus wrote: >>> >>>> *Contact emails* >>>> [email protected] >>>> >>>> *Explainer* >>>> None >>>> >>>> *Specification* >>>> https://w3c.github.io/pointerevents/#the-pointerrawupdate-event >>>> >>>> *Summary* >>>> The PointerEvents spec restricted pointerrawupdate to secure contexts >>>> in 2020, hiding both the event firing and the global event listeners from >>>> insecure contexts. Through this feature, Chrome will match the updated spec >>>> and become interoperable with other major browsers. >>>> >>>> *Blink component* >>>> Blink>Input >>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EInput%22> >>>> >>>> *Web Feature ID* >>>> pointer-events-api <https://webstatus.dev/features/pointer-events-api> >>>> >>>> *TAG review* >>>> None >>>> >>>> *TAG review status* >>>> Not applicable >>>> >>>> *Risks* >>>> >>>> >>>> *Interoperability and Compatibility* >>>> This will improve Interop: Firefox already matches the spec. (Safari >>>> doesn't support pointerrawupdate yet.) The compat risk is non-zero. We >>>> believe the risk is negligible because pointerrawupdate is not a popular >>>> API, and non-secure pages are not expected to be widespread these days. >>>> >>>> *Gecko*: Shipped/Shipping (https://bugzil.la/1550462) >>>> >>>> *WebKit*: No signal >>>> >>>> *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? >>>> None >>>> >>>> >>>> *Debuggability* >>>> None >>>> >>>> *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/pointerevents?label=master&label=experimental&aligned&q=pointerevents%2Fpointerevent_pointerrawupdate >>>> . >>>> >>>> *Flag name on about://flags* >>>> None >>>> >>>> *Finch feature name* >>>> PointerRawUpdateOnlyInSecureContext >>>> >>>> *Non-finch justification* >>>> The finch flag covers only the event firing. The IDL change for the >>>> global event listeners onpointerrawupdate is not behind a flag (because >>>> Blink Extended IDL doesn't allow this). >>>> >>>> *Rollout plan* >>>> Will ship enabled for all users >>>> >>>> *Requires code in //chrome?* >>>> False >>>> >>>> *Tracking bug* >>>> https://crbug.com/404479704 >>>> >>>> *Estimated milestones* >>>> Shipping on desktop 143 >>>> Shipping on Android 143 >>>> Shipping on WebView 143 >>>> >>>> *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/5151468306956288?gate=4786060139823104 >>>> >>>> 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/487895e6-084b-4c54-89da-8fa194a12d94n%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/487895e6-084b-4c54-89da-8fa194a12d94n%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/CAB0cuO7uOx9zUe-qEQUqqNW%3DrORe1yUFyghNoO7b2Of_b50eGg%40mail.gmail.com.
