3 ms·

Still reading through but it mentions, IE7 when, as I've found out recently, going to a 2.x jQuery release will break IE8 functionality which is still used with

by atwebb 12y ago

Still reading through but it mentions, IE7 when, as I've found out recently, going to a 2.x jQuery release will break IE8 functionality which is still used within organizations either as the actual browser or through compatibility mode. I didn't care for the format of the page but do like the author's tone and points so far. I think a lot of the issues people have with jQuery is that (as the article mentions) it's become synonymous with Javascript and abstracts so many things that many people using it don't understand the underlying framework and functions. That and why include more resources if you don't really need to.

jrochkind1 12y ago
There is a lot of misconceptions here. There are two parallel tracks of JQuery maintained, with _identical functionality_, one which supports IE8 and less, one which doesn't. JQuery team is supporting both. If they don't behave identically, that's a bug. If you don't need IE8 or less support, you can use the smaller higher-performance JQuery that doesn't support IE8. If you do need IE8 or before you use the other variant. Your code remains identical either way. JQuery still supports IE8 and less, and has announced no plans to stop. A lot of people are confused about this, and it's made more confusing by their mistakes about version labelling. At present, these two variants are JQuery 1.x (IE8 no problem), and JQuery 2.x (IE9 and above). There are identical parallel versions of each. 1.11.0 and 2.1.1 have identical functionality. Yes, this is super confusing, so going forward in the future, they will call the old-browser-compat variant "JQuery compat", and the no-old-browsers variant "JQuery", and version numbers will be sync'd. http://blog.jquery.com/2014/10/29/jquery-3-0-the-next-generations/ http://blog.jquery.com/2014/10/29/jquery-3-0-the-next-genera... At present, the JQuery team is still committed to maintaining identical functionality in an old-browser-compat variant, and a newer no-old-browser variant, sync'd, for the indefinite future. And in fact they recommend the Compat version "for most web sites, since it provides the best compatibility for all website visitors." They could at some point in the future decide to stop doing so -- they have said they won't do so until usage of older browsers has dropped significantly.
- atwebb 12y ago
  Thanks for the detailed response, that is clearly my mistake. I did an install from NuGet and went with 2.1.1 making an assumption that the latest build was the greatest build and not really doing a lot of research. On my end, it was a browser compatibility mode setting and a meta tag resolved the issue for just my site and is fine for the usecase.
  - jrochkind1 12y ago
    Yep, they've failed at making it clear. Hopefully the change to calling the variants "JQuery Compatibility" and "JQuery" will help -- although since they are still saying they recommend "JQuery Compatibility" for most sites, I think they should have called it "JQuery" (the compatible one) and "JQuery Future" or "Jquery Non-Compatible" or whatever. Anyway, you also could have simply dropped in the equivalent JQuery 1.x version for old-browser-compat with no changes to your code.

by atwebb 12y ago

jrochkind1 12y ago

There is a lot of misconceptions here. There are two parallel tracks of JQuery maintained, with _identical functionality_, one which supports IE8 and less, one which doesn't. JQuery team is supporting both. If they don't behave identically, that's a bug. If you don't need IE8 or less support, you can use the smaller higher-performance JQuery that doesn't support IE8. If you do need IE8 or before you use the other variant. Your code remains identical either way. JQuery still supports IE8 and less, and has announced no plans to stop. A lot of people are confused about this, and it's made more confusing by their mistakes about version labelling. At present, these two variants are JQuery 1.x (IE8 no problem), and JQuery 2.x (IE9 and above). There are identical parallel versions of each. 1.11.0 and 2.1.1 have identical functionality. Yes, this is super confusing, so going forward in the future, they will call the old-browser-compat variant "JQuery compat", and the no-old-browsers variant "JQuery", and version numbers will be sync'd. http://blog.jquery.com/2014/10/29/jquery-3-0-the-next-generations/ http://blog.jquery.com/2014/10/29/jquery-3-0-the-next-genera... At present, the JQuery team is still committed to maintaining identical functionality in an old-browser-compat variant, and a newer no-old-browser variant, sync'd, for the indefinite future. And in fact they recommend the Compat version "for most web sites, since it provides the best compatibility for all website visitors." They could at some point in the future decide to stop doing so -- they have said they won't do so until usage of older browsers has dropped significantly.

atwebb 12y ago
Thanks for the detailed response, that is clearly my mistake. I did an install from NuGet and went with 2.1.1 making an assumption that the latest build was the greatest build and not really doing a lot of research. On my end, it was a browser compatibility mode setting and a meta tag resolved the issue for just my site and is fine for the usecase.
- jrochkind1 12y ago
  Yep, they've failed at making it clear. Hopefully the change to calling the variants "JQuery Compatibility" and "JQuery" will help -- although since they are still saying they recommend "JQuery Compatibility" for most sites, I think they should have called it "JQuery" (the compatible one) and "JQuery Future" or "Jquery Non-Compatible" or whatever. Anyway, you also could have simply dropped in the equivalent JQuery 1.x version for old-browser-compat with no changes to your code.