Rick Byers

Yep, it sounds like we're all on the same page here given the current relaity - thanks!

Ah, ok - that's fine with me, thanks! Let me know if there's anything I can do to help. There are a lot of links out there pointing here (eg....

Yeah everything should be tracked in WHATWG/Dom now, so I think this repo is valuable only from a history perspective. As long as archiving doesn't break URLs, I'm fine with...

Of course an obvious downside of this approach is that it doubles the event dispatch costs, which in the case of `touchmove` can sometimes add up to a non-trivial fraction...

Keeping this open on me for now to build a test page for this once @dtapuska has a working implementation in chromium. I doubt we'll want to add anything to...

Thanks for the report. @dtapuska have you tried your polyfill in Firefox? Newer version of Firefox have the API built-in, but having a working polyfill would still be good IMHO.

> Perhaps EventTarget.supportsEventListenerOptions should actually be used no? There are some cases where you'd like to test whether something supports passive or not. But I think the bulk of the...

> Just thinking out loud here... could we expose the actual dictionaries somewhere as interface objects? > Maybe not exposed on the global, to avoid pollution. But I like a...

Yeah. I'm happy with global in this case. As of Feb 1, the token `EventListenerOptions` occurred exactly never in the Alex top 500k.

> I think EventTarget.EventListenerOptions is good, regardless of any existing (or nonexistent) global EventListenerOptions definition in the wild. It does not belong there, it belongs to event targets. Unfortunately it...