On Mon, Jun 13, 2022 at 1:19 PM Joe Medley <[email protected]> wrote:
> What are the milestones for deprecation and removal? > This removal is on track for M105. > Also does this have a status entry? I can't find one. > That's my fault, I had advised Mehdi that I did not think a chromestatus entry was needed here. For my understanding: is it our policy to have a status entry for all removals (even if minor)? > Joe Medley | Technical Writer, Chrome DevRel | [email protected] | > 816-678-7195 <(816)%20678-7195> > *If an API's not documented it doesn't exist.* > > > On Thu, Jun 9, 2022 at 9:11 AM Mehdi Kazemi <[email protected]> wrote: > >> Contact emails >> >> >> *[email protected] <[email protected]>,[email protected] >> <[email protected]>,[email protected] >> <[email protected]>*Explainer >> >> >> *None*Specification >> >> None. Not a standard feature. >> >> Summary >> >> Gesture Scroll DOM events, namely “gesturescrollstart”, >> “gesturescrollupdate” and “gesturescrollend” are non-standard APIs, which >> were added to Blink for use in plugins, but it appears they were also >> exposed to the web unintentionally. Plugins are no longer web-exposed since >> the deprecation of Google Native Client (NaCl). >> >> WebKit Bug: https://bugs.webkit.org/show_bug.cgi?id=92281 >> >> Changelog: >> https://bugs.webkit.org/attachment.cgi?id=155046&action=prettypatch >> >> Motivation >> >> Currently, this API doesn’t work in all situations. It only works when >> there is a *non-composited scroller*. These events are related to >> compositing state, and compositing state is not meant to have observable >> behavior impact and in Blink will vary depending on display type and other >> factors. >> >> >> Blink component >> >> Blink>Scroll >> <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EScroll&can=2> >> >> >> TAG review >> >> >> TAG review status >> >> Not applicable >> >> >> Risks >> >> No other engine supports these events, so we do not expect >> interoperability issues. >> >> As for compatibility, usage data from Canary, Dev and Beta channels show >> that usage is very low, around 0.000015% (gesturescrollstart >> <https://chromestatus.com/metrics/feature/timeline/popularity/4220> >> gesturescrollupdate >> <https://chromestatus.com/metrics/feature/timeline/popularity/4221> >> gesturescrollend >> <https://chromestatus.com/metrics/feature/timeline/popularity/4222>). >> For this reason we would like to just remove it, without any deprecation >> period. >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >> ? >> >> No >> >> >> Requires code in //chrome? >> >> False >> >> >> Tracking bug >> >> https://crbug.com/1293994 >> <https://bugs.chromium.org/p/chromium/issues/detail?id=1293994> >> >> >> Estimated milestones >> >> No milestones specified >> >> >> >> >> >> >> -- >> 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 on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAASN_%3DmnFnKhp7WQNYiVztF%3Dhr1jpzSTo1x02nXZtysnO2GUMQ%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAASN_%3DmnFnKhp7WQNYiVztF%3Dhr1jpzSTo1x02nXZtysnO2GUMQ%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAjAU%3DYYHfcYftb1%2BeTqBgceADufdeFj5J9RT9uBO6PUJUXqXw%40mail.gmail.com.
