jquip
jquip copied to clipboard
jQuery in Parts
jquip.fn.not is not filtering out elements, but instead is whitelisting
The accessibility plugin for Bootstrap, developed by eBay/PayPal seems to be incompatible with jquip. The respective lines of failing code: `bootstrapaccessibilityplugin/src/js/functions.js`: ``` javascript $.extend( $.expr[ ":" ], { ``` `bootstrapaccessibilityplugin/src/js/alert.js`:...
I just threw jquip into my system instead of jQuery...and straight away saw a problem: ``` ;$['plug']("ajax", function ($) { ``` This line throws an "$.plug is not defined" error....
I am using WebPack to compile my JavaScript resources and alike into a single JavaScript and CSS file. Long story short; I realized how jQuery takes ~250kb of my script....
My GET calls were corrupted with two '?'.
This is probably an IE8 bug/limitation, but jQuery seems to work around it. I'm trying to use the [Chosen component](http://harvesthq.github.io/chosen/) with jQuip instead of jQuery. It seems to mostly work...
We're currently evaluating jquip for our project and I was interested to find out what jquip will be doing when jquery releases 1.9 and 2.0 next year. [As mentioned on...
IE8's `fireEvent` will raise an 'Invalid Argument. ' for events that are not in its predefined list (onclick, onblur, etc.) Fixing would require tracking events outside `addEvent` and bubbling them.
What are thoughts about moving the `loadAsync` parts out of core? It could help compatibility with those who are using other loaders and also trim some size.