I won't be using for a few a years but I am glad it is leading pushing people to CSS3 compliance.
huh?
IE 7 and 8 are still a huge chunk of the market, and they dont support CSS3.
JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
21–30 of 237 posts
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#22Earlier quoted context omitted.
Ok. So, if I upgrade and someone does visit from an older IE browser what happens? :) I'll be back to testing browser differences. I guess those are pretty old browsers, so oh well.
It's pretty simple– if you want to support IE<9, don't upgrade to jQuery 2.x. A lot of people are already dropping support for IE<8.
It's really not that simple. Now you have to check to see if a plugins support 1.9 or 2.0, and plugin writers will have to support both or IE8 supporters will have to live without new plugins.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#23I won't be using for a few a years but I am glad it is leading pushing people to CSS3 compliance.
wat?
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#24I'll play the cynic here and try to diagnose why this is even being considered.
jQuery is a very invasive API. Its goal is to steal all the work from the developer, and to "guarantee" what it deems to be "correct" input for a certain subset of browsers. This approach may ostensibly work, but inevitably falls apart, which leads to thousands of "bugs" being reported.
Because the API has grown to be so massive, goalposts "must" be moved in order to create a lighter API. Once again, this is because of a design flaw. Goalposts will continue to be moved in cyclical fashion unless an alternative design is used. Fellow developers may denigrate me for it, but I will explain how this problem can be avoided.
An API that tries to cater to everyone cannot and will not succeed. This is evidenced by the upcoming "fork". Conversely, an API that provides a set of tools to developers without catering can work in many environments. The burden is then placed upon the developer to choose which environments matter. As has been outlined by mobile developers, object inferences for IE 6 really are unnecessary for mobile Webkit environments. I have written here on this concept before, mostly on the topic of "graceful degradation". Browser specificity can and will kill a client-side API.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#25Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8? I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc. jQuery's main raison d'être might have gone out the window.
The premise is that jQuery 1.9 and 2.0 are API-compatible, so you can do something like: New browsers will get a lighter download and a faster runtime. oldIE will still work with all the hacks required to make it work.
You do realize that IE 10 dropped conditional comments, right?
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#26Earlier quoted context omitted.
The premise is that jQuery 1.9 and 2.0 are API-compatible, so you can do something like: New browsers will get a lighter download and a faster runtime. oldIE will still work with all the hacks required to make it work.
You do realize that IE 10 dropped conditional comments, right?
If you look at the second conditional comment, it will not be parsed as a comment in browsers without conditional comment support.
In other words, it will correctly use jQuery 2.0, like any other browser without conditional comment support.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#27Earlier quoted context omitted.
The premise is that jQuery 1.9 and 2.0 are API-compatible, so you can do something like: New browsers will get a lighter download and a faster runtime. oldIE will still work with all the hacks required to make it work.
You do realize that IE 10 dropped conditional comments, right?
[deleted]
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#28So does this mean that there will be ongoing development in the 1.9 line which will add new features available in the 2.0 line, or is this just the end of the line for IE If that's true, this seems like an odd line in the sand for them to draw. IE9 isn't available before Win7, so it can't die until users upgrade their OS.
According to StatCounter[1], IE8 still represents 13.78% of Worldwide visits (plus 1.4% for IE7; IE6 is just part of 'other' now), and 14.92% of North America (IE7; 1.79%).
[1] http://gs.statcounter.com/#browser_version-ww-monthly-201206...
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#29I don't know if I can get behind this or not. I understand their desire but I don't see this as a viable option just yet. I'm not so concerned with 2.0 and 1.9 as you can load the right one, but what about when 2.1 comes out? Are they going to back-port all the new features to 1.9.1? If not then I now have a big fragmentation issue if I rely on anything specific to 2.1.
Don't forget that IE 8 is the last version XP will get and XP is going to be out there for a long time yet (sadly), especially in corporate environments. Effectively (as far as IE only environments are concerned) JQuery has just set a time limit on proper web access for an entire OS.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#30Earlier quoted context omitted.
You do realize that IE 10 dropped conditional comments, right?
If you look at the second conditional comment, it will not be parsed as a comment in browsers without conditional comment support. In other words, it will correctly use jQuery 2.0, like any other browser without conditional comment support.
It's a conditional conditional comment. I feel ill.