Rick Byers

Chrome desktop always has "touch support". A user could plug in a touch device at any moment, including devtools emulation etc. More commonly many Windows machines appear to have "touch...

😄 Awesome, hadn't seen that one Patrick. BTW you can tell it's performance review season at Google when I start engaging with low-latency on GitHub issues (wishing I still got...

I think we should work on improved filtering in general. Related to some of the other left-nav bugs.

Sorry for the trouble, this is a breaking change in Chrome 56 to [improve scroll performance](https://developers.google.com/web/updates/2017/01/scrolling-intervention). You probably need to add an appropriate `touch-action` [CSS rule](https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action) to explicitly disable touch...

Chrome has never just stopped sending touch events, it sent `touchcancel` to indicate that the touches were now being consumed by the browser to drive scroll. The difference here with...

Thanks for the details Dave. We've been working to align our viewport model with Safari and Edge (and @staktrace has expressed some interest from Firefox), and talking about standardizing in...

@bokand is the chromium expert. Dave?

`MessageEvent.triggeredByUserActivation` (or some such) SGTM. But can you elaborate on your "leak" concern? Isn't it fine for any origin to know at any time whether it's currently inside the context...

Yeah, that was my thinking too. Malte makes a good point that this is probably mainly useful cross-document (because within a single document there's no security boundary - just like...

Thanks for the scenario! In chromium @mustaqahmed is [experimenting](https://bugs.chromium.org/p/chromium/issues/detail?id=696617) with a simpler model for [gestures](https://docs.google.com/document/d/1erpl1yqJlc1pH0QvVVmi1s3WzqQLsEXTLLh6VuYp228/edit#) that should solve most of what you've described. Still, probably worth thinking specifically about explicit...