Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
Programming The Internet

jQuery 3.0 Stops Supporting Internet Explorer Workarounds (softpedia.com) 80

Posted by EditorDavid from the ghost-of-browsers-past dept.
An anonymous reader writes: Thursday's release of jQuery 3.0 is "the first version that features absolutely no workarounds for old Internet Explorer browsers," reports Softpedia. "If customers are still asking you to work with IE6, IE7, and IE8, then you should stick with jQuery 1.0 for the foreseeable future." The jQuery blog explains that over 18 months of development, "We set out to create a slimmer, faster version of jQuery (with backwards compatibility in mind)... It is a continuation of the 2.x branch, but with a few breaking changes that we felt were long overdue." Besides jQuery's free, open source JavaScript library, they also released a "slim" version that excludes ajax and effects modules (as well as deprecated code), and a new version of the jQuery Migrate plugin.
This discussion has been archived. No new comments can be posted.

jQuery 3.0 Stops Supporting Internet Explorer Workarounds More

jQuery 3.0 Stops Supporting Internet Explorer Workarounds

Comments Filter:

  • Great decision (Score:5, Funny)

    by Anonymous Coward on Saturday June 11, 2016 @08:38AM (#52294581)

    Now they need the guts to stop supporting JavaScript.

    • Without JavaScript, HTML documents would have to be static, and apps would have to be native. Would you prefer having to download a separate native app for each Internet service you access through your PC? Would you further prefer having to buy another operating system license or possibly even another computer* if the app happens to be exclusive to an operating system other than the one your PC runs?

      * OS X is exclusive** to Mac computers, which start at $499.
      ** Legally.

  • So it's useless in the real world. (Score:1)

    by Anonymous Coward

    "If customers are still asking you to work with IE6, IE7, and IE8, then you should stick with jQuery 1.0 for the foreseeable future."

    So jQuery 3 is useless in the real world, then, since we need to support at least some of those browsers. Over 15% of my sites' users are using IE 8. I can't tell them to "fuck off" by using jQuery 3! Hell, I still get more IE 8 users than I get Firefox users.

    jQuery 1 will be the only option for a very long time.

    • Re: (Score:2, Interesting)

      by Anonymous Coward

      So? You made the decision to use Microsoft technologies. Full stop.

      That's like whining about gas mileage standards when you own a Hummer. The rest of the world shouldn't bow to your special snowflake existence.

      Sorry that's harsh...but it's also how reality works.

      Captcha: incensed

      • Re:So it's useless in the real world. (Score:5, Insightful)

        by Shados ( 741919 ) on Saturday June 11, 2016 @09:12AM (#52294733)

        No, it really IS useless.

        If you only target modern browsers, between querySelectorAll, XHR2 or fetch (ok, that will need polyfilling), and all the newer stuff that's available in 95% of browsers, jquery is very nearly useless.

        The only reason to use it is to deal with older browser quirks. Once you don't need to support that, you don't need jquery.

      • So? You made the decision to use Microsoft technologies. Full stop.

        15% of the *customers* are using IE8.

        What exactly is he supposed to do?

        Use an IE8 exploit to do a drive-by download of Chrome and force it to be the default browser?

    • Re:So it's useless in the real world. (Score:4, Informative)

      by ledow ( 319597 ) on Saturday June 11, 2016 @09:55AM (#52294843) Homepage

      Well, judging from any quick search of release notes for just about every service I look into, they are unlikely to be able to online bank, use Google services, use quite a lot of modern websites, Google and Bing will be whinging at them constantly, and most websites will look like shit or just not work at all.

      Sure, it's nice to retain compatibility, but there's also a time to move on. Do you still push out Windows 3.1 apps? Do you test on Windows 95? Still using plugins from the 90's?

      If you haven't noticed, without an HTML5 browser (all the plugins are dead now by the way - Java, ActiveX, etc. - only Flash really "works" at all and that's going) almost all the websites you visit are just broken.

      So if you ask your users to move on to a modern browser, you won't be the first to ask them that, by a long shot, and that's warning enough itself.

      As someone who works in education, where they never throw anything away if it can still be used in lessons, where I'm often asked to install CDs that have been lying around for 20 years or more (Shockwave anyone?), with teachers complaining they can't teach what they used to 20 years ago because they don't have that software (yeah, I know, don't go there), almost everything is now HTML5 - from both paid and free resources. Even the CDs have gone and everything's now web-based, even testing, assessment, etc. tools.

      And this year, pretty much every supplier announced HTML5 versions because NOTHING ELSE works on an iPad - Flash, etc. Our banks enforce IE 10 minimum but recommend Firefox or Chrome.

      These 15%? Yeah, they're not your main source of income if they haven't bought a PC or upgraded their browser in 10 years.

      • They are Chinese. Unless your site needs Mandarin it is safe to ignore

      • Re: (Score:1)

        by Gr8Apes ( 679165 )

        Our banks enforce IE 10 minimum but recommend Firefox or Chrome.

        These 15%? Yeah, they're not your main source of income if they haven't bought a PC or upgraded their browser in 10 years.

        IE8 is 7 years old. I haven't supported IE 8 in 3 years. We ran tests via a QA person only to note that if the website broke, we'd add IE8 to the automatic pop up "Your browser is not supported, not all aspects of the site may work. Please upgrade to a supported browser: blah blah blah". It failed on a page about 2 years ago, we added the popup, and amazingly IE8 usage dropped significantly. :) No, we didn't lose those IE8 folks, they migrated to a supported browser. Since they were paying for services, the

    • At work we have Chrome everywhere now. Reason being is IE 8 in the past year has stopped working for a large number of websites!

      Shit even ADP credit card processing for customers or to print out our paystubs just stopped working.

      IE 8 users see the writing on the wall for the past year now and won't blame you if everyone else including IE's own default MSN page doesn't support it!

    • Re:So it's useless in the real world. (Score:5, Informative)

      by Barefoot Monkey ( 1657313 ) on Saturday June 11, 2016 @12:02PM (#52295323)

      <!--[if lte IE8]> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script> <![endif]-->
      <!--[if !lte IE8]> <!--> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.0.whatever/jquery.min.js"></script> <!-- <![endif]-->

      If I typed that correctly then it should give users on IE8 and below jQuery 1, while everyone else gets jQuery 3 even if their browsers don't support conditional comments. Just be sure not to use any functionality that's not in the jQuery 1 version that you use, but that should be easy.

      • Re: (Score:3)

        by unrtst ( 777550 )

        Just be sure not to use any functionality that's not in the jQuery 1 version that you use, but that should be easy.

        Someone should put together some sort of high level library to make this seamless and cover the edge cases for compatibility. It could even include some fancy wrappers for common stuff. JQScript?

    • http://caniuse.com/usage-table [caniuse.com]

      15% on IE 8 just isn't typical. I believe most IE 8 usage is in China. But they are supporting jQuery 1.0 for you. But you are still mad because they made something for everyone else?

    • Over 15% of my sites' users are using IE 8.

      On which operating system is Internet Explorer 8 still receiving security fixes? Windows XP and Windows Server 2013 are no longer supported. Nor are IE pre-9 on Windows Vista and IE pre-11 on Windows 7. And unlike other applications that require operating system versions that no longer receive security fixes, an application with "Internet" in its name can't reasonably be air-gapped from the Internet. Continuing to cater to IE 8 enables users' continued use of vulnerable software that puts their information

    • Why do we cave to people who want to use ancient unsupported stuff? Microsoft does not even support this stuff any more, and it's only used in places like banks where some idiot is in charge of IT and insists on 'standardizing' on something that is unsupported and a security nightmare. I support a VERY large application that is designed for Fortune 500 companies, and we simply tell them old IE is unsupported because it is not HTML5 compliant. Use Chrome, Firefox, or Edge. We get one second of pushback u

  • The pain (Score:1)

    by Anonymous Coward

    If customers are still asking you to work with IE6, IE7, and IE8, then you should stick them with a fork. They're done for.

  • And nothing of value was lost (Score:3)

    by RogueWarrior65 ( 678876 ) on Saturday June 11, 2016 @09:02AM (#52294703)

    Now, if Flash would finally go away...

  • Windows XP and Vista (Score:5, Informative)

    by CritterNYC ( 190163 ) on Saturday June 11, 2016 @09:44AM (#52294809) Homepage
    Essentially, all jQuery has done is drop support for Internet Explorer on Windows XP and Vista. Fully updated, XP runs IE8 and Vista runs IE9. Google Chrome did the same thing 2 months ago when it started requiring Windows 7 and up. Windows XP support was dropped a long time ago. Vista is still supported, but only used by a small chunk of users worldwide (about 1.4%). While XP still has a larger worldwide userbase (around 10%), most companies and individuals don't consider them worth supporting or advertising/marketing/selling to.

    jQuery does still support both IE10 and IE11, so it's not like they're dropping all IE workarounds as stated in the title.

  • Supporting quirks is what it's FOR (Score:1)

    by Anonymous Coward

    The only reason I use jQuery is to smooth over browser oddities. If it doesn't do that then it has no other value. I totally don't understand this decision.

    Yes, MSIE is very low marketshare. Yes, MSIE sucks, so fuck that. jQuery was the [partial] answer. Apparently newer versions are no longer that.

    Maybe another way to look at it, would be this: if you use jQuery 3, what do you use it for? Why bother at all? It doesn't get you anything, or at least, it won't get me anything.

    • Syntactic sugar, avoiding yet another learning cycle for just a little longer, maintaining existing codebases.

    • CSS selectors are MUCH easier than using document.getElementsByTagName, document.getElementsByClassName, document.getElementById. Those are all a mouthful when I can just type $(".className") and be done with it and have terser code that is easier to read (if you know jQuery).

      jQuery's chaining also makes it a lot easier and nicer looking to manipulate DOM elements, unless you really hate chaining I guess. var x = document.createElement("input"); x.type = "checkbox"; x.checked = false; x.click = //etc; OR $(

      • Re: (Score:2)

        by Shados ( 741919 )

        Not contesting the other arguments, but for the first one...

        CSS selectors are MUCH easier than using document.getElementsByTagName, document.getElementsByClassName, document.getElementById. Those are all a mouthful when I can just type $(".className") and be done with it and have terser code that is easier to read (if you know jQuery)

        document.querySelectorAll does just that. If it's too much to type, just alias it. Even to the $ sign!

    • Comment removed based on user account deletion

  • I'd like to see benchmarks for the areas of jQuery where they claim performance increased, but I can't find any..

  • Will newer version allow use of Content-Security-Policy [wikipedia.org] without script-src unsafe-eval ?

Slashdot Top Deals

No spitting on the Bus! Thank you, The Mgt.

Close