-
-
Notifications
You must be signed in to change notification settings - Fork 408
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
Make jQuery Optional #73
Conversation
|
||
- How would the core team like to handle the 'make it optional' switch? May affect the build process, | ||
library requirements etc. | ||
- The FF11 requirement, what is the minimum supported version of FF? Is it fine to drop? (FF is on ~38 now) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FF11 marketshare is > 0%
https://www.netmarketshare.com/report.aspx?qprid=3&qpaf=&qpcustom=Firefox+11&qpcustomb=0
One approach the Angular team takes is to use Google's jqLite library if jQuery itself isn't loaded. Is it worth investigating to see if a similar approach can be taken for Ember? This can also be exposed for developers. If a developer invokes |
Related: emberjs/ember.js#3791 |
Related #86 removes most of the reliance on jQuery for eventing. In my current implementation, https://github.com/runspired/ember-capture-eventing/blob/master/addon/event_dispatcher.js#L379 |
Update 0000-jquery-optional.md
Related: https://github.com/rwjblue/ember-native-dom-event-dispatcher Haven't tried it yet, but assuming it works, it's a bridge to be rid of jQuery. |
Link to rendered RFC