3 ms·

On how much browsers has this stuff been tested ? because that's the point of jQuery , you can trash it all you want jQuery has been battle tested on a large nu

by camus 13y ago

On how much browsers has this stuff been tested ? because that's the point of jQuery , you can trash it all you want jQuery has been battle tested on a large number of browsers and plateforms. Other DOM frameworks not so much, that's why they fail.

bachback 13y ago
the very point of this is to lose some the old painful browsers (IE6/7/8) to make code much better. almost all work in cross-browser stuff is IE6-8. think of jQuery mainly as a bugfix for old IE's.
- esailija 13y ago
  That is a really gross exaggeration. jQuery only lost 10% of its size on full builds when it eliminated IE6-8. There is still plenty of stuff left to handle. Naive code that only handles common success case is of course going to be small. Even if the modern browsers didn't have bugs and behaved exactly the same, you would still have most of the stuff there. jQuery features amazing event model with endless corner cases and optimizations* handled, powerful ajax library (Think of stuff like prefilters and transports) and so on. * For example your typical delegation implementation traverses the propagation path over and over again for each handler, while probably not even checking for simple selectors.
- wingspan 13y ago
  I don't think this is true: "jQuery Core has more lines of fixes and patches for WebKit than any other browser." [1] [1] http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.html http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.ht...
grey-area 13y ago
There is a test suite, you could easily test it yourself by downloading: https://github.com/nbubna/HTML/tree/master/test https://github.com/nbubna/HTML/tree/master/test Looks like it passes on the latest FF and Safari, though I saw a couple of fails on the latest Chrome. Haven't tried IE, and it definitely won't work on older IE.
- nadabu 13y ago
  Yeah, i'm still hacking on this a lot. It's not v1.0 ready. The Chrome tests pass again, but the alter module still needs some work. And the new event module needs docs, and so on and so on... :)

by camus 13y ago

bachback 13y ago

the very point of this is to lose some the old painful browsers (IE6/7/8) to make code much better. almost all work in cross-browser stuff is IE6-8. think of jQuery mainly as a bugfix for old IE's.

esailija 13y ago
That is a really gross exaggeration. jQuery only lost 10% of its size on full builds when it eliminated IE6-8. There is still plenty of stuff left to handle. Naive code that only handles common success case is of course going to be small. Even if the modern browsers didn't have bugs and behaved exactly the same, you would still have most of the stuff there. jQuery features amazing event model with endless corner cases and optimizations* handled, powerful ajax library (Think of stuff like prefilters and transports) and so on. * For example your typical delegation implementation traverses the propagation path over and over again for each handler, while probably not even checking for simple selectors.
wingspan 13y ago
I don't think this is true: "jQuery Core has more lines of fixes and patches for WebKit than any other browser." [1] [1] http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.html http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.ht...

grey-area 13y ago

There is a test suite, you could easily test it yourself by downloading: https://github.com/nbubna/HTML/tree/master/test https://github.com/nbubna/HTML/tree/master/test Looks like it passes on the latest FF and Safari, though I saw a couple of fails on the latest Chrome. Haven't tried IE, and it definitely won't work on older IE.

nadabu 13y ago
Yeah, i'm still hacking on this a lot. It's not v1.0 ready. The Chrome tests pass again, but the alter module still needs some work. And the new event module needs docs, and so on and so on... :)