Rick Byers
Rick Byers
> I'm curious to hear others' thoughts. As long as folks are convinced it's really best for this to be sender opt-in, then I'm happy with @dtapuska's proposal!
Why don't we start by adding an extended-attribute that opts dictionaries into this behavior? We can try that out in a few cases, then revisit if/how to change the default.
Not if the only use of the enum is in a method argument (same as the dictionary issues we're discussing).
Do we want to allow enumeration of supported dictionary/enumeration members? I can see arguments either way, without a compelling use case I'd probably prefer we keep this scoped to feature...
> I'm confused - enumerating the supported dictionary members is literally the request here. (Or at least, being able to ask if a given name is a supported dictionary member.)...
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...
And `touch-action: none` should be all you need to disable scrolling on an element (unless you've got some weird case where a descendant of that element has, eg. `overflow:auto` -...
> What kind of support are you looking for? I don't presume to know enough about event handling in jQuery and the typical usage patterns to have a valuable opinion...
> You can get pretty close to that today with special events: http://jsbin.com/bupesajoza/edit?html,js,output Interesting, thanks. Anyway I'll leave it to you jQuery experts to figure out what, if anything, you...
You might want to consider polyfilling the visible effect of "passive" on browsers that don't support it. This will reduce the chance of code working fine in old browsers but...