31–40 of 48 posts
VENDOR-PREFIXED CSS PROPERTIES So there are CSS properties with vendor specific implementation, how are they going to handle that? Also what if the browser (like Chrome) changes its spec.? This could break your current code.
Global ajax events: ( are being removed ) Events such as ajaxStart fired by $.ajax can currently be attached to any element–even to elements that are not in a document at all! This creates an inefficient special case, so we will eventually remove that ability and fire ajax events only on document. I need to look into this. If you are using jQuery outside of a standard browser environment this might be problematic.
Wouldn't you be using the callback or Promise for those cases?
A lot of good changes in here. The modularity will improve usability -- particularly for sites who want the core jQuery features without all the extras. My hope is this will make it easier to use jQuery on mobile -- and more comparable to Zepto in terms of size. I remember reading somewhere that 1.8 would drop support for quirks mode in IE. Anybody know if this ended up happening? I didn't see any mention in this pos…
jQuery never really "supported" quirks mode, the unit tests were not ever run in quirks for example. A few of the offset and dimensional tests tried to account for quirks, but we gave up on that totally in 1.8 in favor of fully supporting the CSS box-model property. Many Quirks pages could still use jQuery 1.8 successfully if they avoid asking for dimensional measurements, but I'm not sure why developers would still…
Earlier quoted context omitted.
I suppose you write all your code in assembly too? There's no room for going higher-level than the APIs exposed by the browser?
I'm just curious what the higher-level APIs are that people need from jQuery that aren't available on mobile. I recall jQuery being popular for selector queries (available on all mobile browsers natively with querySelector and querySelectorAll) and for even listeners (offers no real advantage over addEventListener as far as I can tell).
"jQuery is now powering about one-half of all the major web sites on the Internet" Anybody have any data on this?
So to say jQuery "powers" half the major websites on the Internet is like saying "Cup holders power 99% of all passenger vehicles world-wide".
"jQuery is now powering about one-half of all the major web sites on the Internet" Anybody have any data on this?
http://wappalyzer.com/categories/javascript-frameworks
It's a different statistic but does make the 50% seem reasonable.
Global ajax events: ( are being removed ) Events such as ajaxStart fired by $.ajax can currently be attached to any element–even to elements that are not in a document at all! This creates an inefficient special case, so we will eventually remove that ability and fire ajax events only on document. I need to look into this. If you are using jQuery outside of a standard browser environment this might be problematic.
Looks like they are not being removed but that you should attach to document only.
I must admit that I'm surprised $.browser is going to disappear in 1.9, not because removing it is a bad thing, but because of the number of scripts that is going to break. Current jQuery UI, Bootstrap etc all use $.browser. There is presumably plenty of time before 1.9 for library authors to address this, but I can certainly see a lot of breakage coming.
I still don't think it is a bad thing to remove $.browser since it does encourage good code practice, but there is a lovely irony that to decrease code size in jQuery core, plug-ins will likely need to have increase their size.