3 ms·

> For instance, in Chrome for Android 80% of the touch events that block scrolling never actually prevent it I'm curious how they get at this data. I haven't f

> For instance, in Chrome for Android 80% of the touch events that block scrolling never actually prevent it I'm curious how they get at this data. I haven't fully thought it through, but something about this raises the "creepy flag" in my head. Does this data come through the "Automatically send usage statistics and crash reports to Google" setting? Google's help page [1] regarding that doesn't seem to indicate it's recording information about website's javascript. [1]: https://support.google.com/a/answer/151135?hl=en https://support.google.com/a/answer/151135?hl=en EDIT: I'd also be curious if they have done any analysis to see if the mechanism that gathers this data is related to the performance implications of touchEvent listeners.

twiss 9y ago
They measure lots of client-side feature usage, in part so that they know when they can deprecate something. Here's a list and short explanation [0]. Firefox has something similar [1] as part of Telemetry, although they measure less things [2]. [0]: https://chromium.googlesource.com/chromium/blink/+/master/Source/core/frame/UseCounter.h#47 https://chromium.googlesource.com/chromium/blink/+/master/So... [1]: http://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/collection/use-counters.html http://gecko.readthedocs.io/en/latest/toolkit/components/tel... [2]: https://dxr.mozilla.org/mozilla-beta/source/obj-x86_64-pc-linux-gnu/dom/base/UseCounterList.h https://dxr.mozilla.org/mozilla-beta/source/obj-x86_64-pc-li...
fenomas 9y ago
The Chrome team probably runs some kind of automated conformance tests over various popular websites, so absent other information it would be simpler to assume that's where this data point comes from. (Though with that said, 80% seems surprisingly low. I can't think why a site would cancel a scroll event besides scrolljacking, and while that's getting more common surely it can't be on 20% of all sites?)

twiss 9y ago

They measure lots of client-side feature usage, in part so that they know when they can deprecate something. Here's a list and short explanation [0]. Firefox has something similar [1] as part of Telemetry, although they measure less things [2]. [0]: https://chromium.googlesource.com/chromium/blink/+/master/Source/core/frame/UseCounter.h#47 https://chromium.googlesource.com/chromium/blink/+/master/So... [1]: http://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/collection/use-counters.html http://gecko.readthedocs.io/en/latest/toolkit/components/tel... [2]: https://dxr.mozilla.org/mozilla-beta/source/obj-x86_64-pc-linux-gnu/dom/base/UseCounterList.h https://dxr.mozilla.org/mozilla-beta/source/obj-x86_64-pc-li...

fenomas 9y ago

The Chrome team probably runs some kind of automated conformance tests over various popular websites, so absent other information it would be simpler to assume that's where this data point comes from. (Though with that said, 80% seems surprisingly low. I can't think why a site would cancel a scroll event besides scrolljacking, and while that's getting more common surely it can't be on 20% of all sites?)