Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / WICG/EventListenerOptions issues and pull requests

#62 - Should this repo be set to "archived"?

Issue - State: open - Opened by patrickhlauke over 6 years ago - 6 comments

#61 - Update note about Modernizr detect

Pull Request - State: closed - Opened by OliverJAsh over 6 years ago - 5 comments

#60 - Remove "test" alive eventListener in example

Pull Request - State: closed - Opened by raphamorim almost 7 years ago - 2 comments

#59 - Spelling

Pull Request - State: closed - Opened by bschnelle about 7 years ago - 2 comments

#58 - Update DOM standard link

Pull Request - State: closed - Opened by domfarolino over 7 years ago - 2 comments

#57 - Publish polyfill to NPM

Issue - State: open - Opened by appsforartists over 7 years ago

#56 - Swiping horizontally in iOS 10

Issue - State: closed - Opened by Cap32 over 7 years ago - 2 comments

#55 - Update feature detection options in explainer.md

Pull Request - State: closed - Opened by rafgraph almost 8 years ago - 2 comments

#54 - Warning keeps showing when using preventDefault?

Issue - State: closed - Opened by alvarotrigo almost 8 years ago - 3 comments

#53 - Make it easier to target non-passive event listeners to specific classes

Issue - State: closed - Opened by bmaurer about 8 years ago - 10 comments

#52 - Use the original context when calling super methods.

Pull Request - State: closed - Opened by aghassemi about 8 years ago - 7 comments

#51 - Modernizr.passiveeventlisteners does not exist?

Issue - State: closed - Opened by enjikaka about 8 years ago - 6 comments

#50 - Polyfill does not work in Safari 9.1.1

Issue - State: closed - Opened by enjikaka about 8 years ago - 4 comments

#49 - CFC to migrate to the Web Platform WG

Issue - State: open - Opened by marcoscaceres over 8 years ago - 9 comments

#48 - fix(polyfill): needsWrapping should init to false

Pull Request - State: closed - Opened by marcoscaceres over 8 years ago - 1 comment

#47 - explainer: video embed & updated browser support

Pull Request - State: closed - Opened by paulirish over 8 years ago - 1 comment

#46 - Polyfill doesn't work in firefox 47

Issue - State: open - Opened by marcog83 over 8 years ago - 1 comment

#45 - Improved feature detection

Pull Request - State: closed - Opened by paulirish over 8 years ago - 3 comments

#44 - Could/should the polyfill simply rewrite/extend addEventListener?

Issue - State: closed - Opened by patrickhlauke over 8 years ago - 3 comments

#43 - fix typo (opqaue)

Pull Request - State: closed - Opened by ghost over 8 years ago - 1 comment

#42 - Minor editorial/syntax tweaks

Pull Request - State: closed - Opened by patrickhlauke over 8 years ago - 1 comment

#41 - Fix broken bullet list structure, replace "eg"

Pull Request - State: closed - Opened by patrickhlauke over 8 years ago - 2 comments

#40 - Tweak to intro and "removing the need" sections

Pull Request - State: closed - Opened by patrickhlauke over 8 years ago - 2 comments

#39 - Add library which generates "touchstarted" events

Issue - State: open - Opened by RByers over 8 years ago - 1 comment

#38 - Add library to make touch listeners passive by default

Issue - State: open - Opened by RByers over 8 years ago

#37 - Request for an Update Demo File to be added to this Repository

Issue - State: closed - Opened by ghost over 8 years ago - 3 comments

#36 - Make the feature detection a bit more legible

Pull Request - State: closed - Opened by marcoscaceres over 8 years ago - 1 comment

#35 - Fix typo

Pull Request - State: closed - Opened by montogeek over 8 years ago - 1 comment

#34 - Should preventDefault not be exposed on passive event handlers?

Issue - State: closed - Opened by rik over 8 years ago - 9 comments

#33 - passive is ambiguous

Issue - State: closed - Opened by rik over 8 years ago - 14 comments

#32 - Fix README.md Polyfill link

Pull Request - State: closed - Opened by Calyhre over 8 years ago - 4 comments

#31 - Add simpler feature detection mechanism?

Issue - State: open - Opened by RByers over 8 years ago - 21 comments

#30 - You are causing SyntaxError in older IE

Pull Request - State: closed - Opened by WebReflection over 8 years ago - 4 comments

#29 - Replaced use of "promise"

Pull Request - State: closed - Opened by jakearchibald over 8 years ago - 2 comments

#28 - Should passive listeners be able to stopPropagation?

Issue - State: closed - Opened by tdresser over 8 years ago - 3 comments

#27 - Should the passive option be part of the event listener key

Issue - State: closed - Opened by RByers over 8 years ago - 33 comments

#26 - Fix some minor spelling and style issues

Pull Request - State: closed - Opened by tdresser almost 9 years ago - 1 comment

#25 - Write explainer doc

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment

#22 - Why do we believe making mayCancel false as a default is at all backward-compatible?

Issue - State: closed - Opened by domenic about 9 years ago - 12 comments

#21 - Safe to change behavior of addEventListener(type, callback, object)?

Issue - State: closed - Opened by foolip about 9 years ago - 21 comments

#20 - UAs observing the presence of event listeners is bad

Issue - State: closed - Opened by foolip about 9 years ago - 48 comments

#19 - Rework spec into the DOM standard

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment

#18 - Consider new names for addEventListener and removeEventListener

Issue - State: closed - Opened by RByers about 9 years ago - 5 comments

#17 - Invert 'mayCancel' to 'passive', making it consistently false by default

Issue - State: closed - Opened by RByers about 9 years ago - 14 comments

#16 - Better feature detection: getSupportedListenerOptions is weird

Issue - State: closed - Opened by smaug---- about 9 years ago - 8 comments
Labels: spec

#15 - booleans should default to false

Issue - State: closed - Opened by domenic about 9 years ago - 1 comment
Labels: spec

#14 - Replace mayCancel with blocksScroll?

Issue - State: closed - Opened by RByers about 9 years ago - 6 comments
Labels: spec

#13 - bikeshed: mayCancel is a confusing name for some use cases

Issue - State: closed - Opened by ojanvafai about 9 years ago - 4 comments

#12 - Should the API be forwards compatible?

Issue - State: closed - Opened by RByers about 9 years ago - 144 comments

#11 - Rather than overload the 3rd argument of addEventListener could we overload the 2nd?

Issue - State: closed - Opened by RByers about 9 years ago - 34 comments
Labels: spec

#10 - getSupportedListenerOptions returning a dictionary whose values are meaningless is odd

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment
Labels: spec

#9 - Having a tri-state requireCancelable is overly complex

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment
Labels: spec

#8 - Need some mechanism for feature detection

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment
Labels: spec

#7 - should requireCancelable be an enum?

Issue - State: closed - Opened by RByers about 9 years ago - 2 comments
Labels: spec

#6 - Should event timing implications be explicit?

Issue - State: open - Opened by RByers about 9 years ago - 1 comment

#5 - Clarify role of EventListenerOptions in identifying handlers

Issue - State: closed - Opened by RByers about 9 years ago - 5 comments
Labels: spec

#4 - should addEventListener throw on invalid requireCancelable value?

Issue - State: closed - Opened by RByers about 9 years ago - 3 comments
Labels: spec

#3 - Is preventDefault being silently ignored on uncancelable events too error-prone?

Issue - State: closed - Opened by RByers about 9 years ago - 19 comments

#2 - Is modifying the value of cancelable OK?

Issue - State: closed - Opened by RByers about 9 years ago - 38 comments

#1 - Shouldn't be overloading addEventListener on partial interface

Issue - State: closed - Opened by RByers about 9 years ago - 1 comment
Labels: spec