-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event type flexibility #51
Conversation
Hey, that's really cool! I'll look into it more thoroughly tomorrow, but looks like an easy merge :) |
e6504b0
to
30ada00
Compare
…-click-outside into element-modifier * 'element-modifier' of https://github.com/crowjonah/ember-click-outside: update readme allow legacy mixin to specify eventType too change named param to eventType allow named param "event" add failing test update lockfile Release v1.2.0-beta.0
I'll investigate why tests are suddenly failing, then merge right after |
Yeah, I looked briefly at the master branch and it looks like some of the latest and greatest modifier stuff might preclude earlier versions of ember and/or node. I see you have the modifier manager polyfill, though, so I'm not sure what the culprit could be. It could also be that a parser/babel upgrade is needed! |
* master: update node for travis fix lint update more deps and node update dependencies Revert "bump node version, remove legacy ember scenarios" bump node version, remove legacy ember scenarios
I've merged the lastest from |
@crowjonah Released as Thanks for the GREAT contribution!! |
The app I work on is currently using a fork of the mixin that allows for flexibility in the event to which the listener is bound (and removed). This is especially handy when something like a modal or popup is overlapping a large amount of an interactive element (in our case a map, where clicking and dragging pans across it).
I've just picked up the modifier work here in anticipation of the deprecation of mixins (emberjs/rfcs#528), and extended the event flexibility to this implementation.
I think this may also solve #48, and relates to #49
Note: dependencies haven't changed, but I did need to regenerate the lockfile in order to get tests to pass in the current state of your branch.