EventListenerOptions
EventListenerOptions copied to clipboard
WICG
An extension to the DOM event pattern to allow authors to disable support for preventDefault
As work on this has migrated/merged to WHATWG, should we use github's archive feature to make it read-only, and somehow amend the readme to call this out a bit more...
It seems that `EventListenerOptions` has gotten wide backing from browser vendors, with Blink, Gecko, WebKit implementations underway or shipping 🎉 . This makes it a good candidate to [migrate](https://wicg.github.io/admin/intent-to-migrate.html) to...
Hi, I was exited about EventListenerOptions, so I started use this polyfill in my project. It works fine in all my supported browser, but firefox . I don't know exactly...
Thinking about how to make it easier to get the perf benefits of passive touch listeners, I'm thinking it would be helpful to publish a sample library which makes all...
Like #38, another library useful for easy adoption would be to expose a new set of events: `touchstarted` and `touchmoved` (like the API discussed in #24) or `aftertouchstart` and `aftertouchmove`....
There's lots of concern in #12 about the complexity of dictionary-member based feature detection. Perhaps we should be designing something simpler, ideally as a general pattern since dictionary-based APIs are...
Even though requiresCancelable=false allows scrolling to proceed without blocking on JS, that should not mean that developers will see the touch events at a location/target different from what the user...