{"action":"created","issue":{"url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/31","repository_url":"https://api.github.com/repos/WICG/EventListenerOptions","labels_url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/31/labels{/name}","comments_url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/31/comments","events_url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/31/events","html_url":"https://github.com/WICG/EventListenerOptions/issues/31","id":147013318,"number":31,"title":"Add simpler feature detection mechanism?","user":{"login":"RByers","id":1280419,"avatar_url":"https://avatars.githubusercontent.com/u/1280419?v=3","gravatar_id":"","url":"https://api.github.com/users/RByers","html_url":"https://github.com/RByers","followers_url":"https://api.github.com/users/RByers/followers","following_url":"https://api.github.com/users/RByers/following{/other_user}","gists_url":"https://api.github.com/users/RByers/gists{/gist_id}","starred_url":"https://api.github.com/users/RByers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RByers/subscriptions","organizations_url":"https://api.github.com/users/RByers/orgs","repos_url":"https://api.github.com/users/RByers/repos","events_url":"https://api.github.com/users/RByers/events{/privacy}","received_events_url":"https://api.github.com/users/RByers/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-04-08T19:13:16Z","updated_at":"2016-04-08T19:46:58Z","closed_at":null,"body":"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 being used / extended everywhere on the web now.\r\n\r\nI originally had a `getSupportedListenerOptions()` API that was easier to use, which we \"fixed\" in #16.  But maybe we should really be thinking of a better pattern?  Some have suggested `EventTarget.supportsPassive`.  This is kind of similar to [DOMTokenList.supports](https://dom.spec.whatwg.org/#dom-domtokenlist-supports) and [CSS @supports](https://developer.mozilla.org/en/docs/Web/CSS/@supports).\r\n\r\nSuggestions?"},"comment":{"url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/comments/207574980","html_url":"https://github.com/WICG/EventListenerOptions/issues/31#issuecomment-207574980","issue_url":"https://api.github.com/repos/WICG/EventListenerOptions/issues/31","id":207574980,"user":{"login":"phistuck","id":184400,"avatar_url":"https://avatars.githubusercontent.com/u/184400?v=3","gravatar_id":"","url":"https://api.github.com/users/phistuck","html_url":"https://github.com/phistuck","followers_url":"https://api.github.com/users/phistuck/followers","following_url":"https://api.github.com/users/phistuck/following{/other_user}","gists_url":"https://api.github.com/users/phistuck/gists{/gist_id}","starred_url":"https://api.github.com/users/phistuck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phistuck/subscriptions","organizations_url":"https://api.github.com/users/phistuck/orgs","repos_url":"https://api.github.com/users/phistuck/repos","events_url":"https://api.github.com/users/phistuck/events{/privacy}","received_events_url":"https://api.github.com/users/phistuck/received_events","type":"User","site_admin":false},"created_at":"2016-04-08T19:46:58Z","updated_at":"2016-04-08T19:46:58Z","body":"> we pollute the global with the interface name already\r\nDo we? `undefined` in Chrome 49.\r\n\r\nI 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.\r\nRegarding `passive` support on a certain `EventTarget` subclass, `WheelEvent.EventListenerOptions` can have a different dictionary, or maybe `WheelEvent.supportedEventListenerOptions.passive` will be `true`."}}