Search jQuery

jQuery Forum

gerry.low..

issue with 2.1.0 and ie

in Using jQuery • 8 years ago

details & steps to reproduce: http://forums.asp.net/post/5626631.aspx

i'm new here, so sorry if i'm posting in the wrong place.

Summary: package id="jQuery" version="2.1.0" targetFramework="net45" />

NuGet 2.1.0 breaks ASP.NET MVC5 applications in vs2013 editions but apparently only for ie.

Sorry but i do not know the jQuery community -- i'm reporting this here in the hope that someone (or many someones) can fix this in a timely fashion.

FWIW, i realize browser specific issues are substantially more nightmarish than browser generic issues.

HELP!!! and thank you for listening. /Gerry

Replies(12)

jakecigar

Re: issue with 2.1.0 and ie

8 years ago

To force IE10 to use the best mode it can, add this meta tag…

<meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1" />

And make sure you use a doctype at the top. Like …

<!DOCTYPE html>

Other than that, you will have to better explain what the problem is, and share a link to a misbehaving page.

JΛ̊KE

gerry.low..

Re: Re: issue with 2.1.0 and ie

8 years ago

JakeCigar ...this video (which does not like ie10 but is happy in Firefox 27.0) explains the problem visually and shows YOUR excellent fix; you can recreate it with Microsoft's free vs2013 express for the web.

http://twitpic.com/dvcq5d Jake, your cigar saved my butt (intentional pun).

Very much appreciated.

Thank you.

Gerry

P.S.: will anyone endeavour to actually fix this or will Microsoft just point fingers are jQuery?

i suspect many programmers are about to get bitten by this bug.

jakecigar

Re: issue with 2.1.0 and ie

8 years ago

Microsoft created that meta tag. It should not be necessary at all. You have to take an extra class after the MSCP to get that bit of info.

JΛ̊KE

Greg Litt..

Re: issue with 2.1.0 and ie

8 years ago

Thanks for the fix.

the ";chrome=1" part might not be needed.

Is this being considered as a bug?

A graceful failure message like "Your IE 10 is in compatibility mode, so this is going to end badly." would have saved me 2 days of hair pulling.

I would suggest a similar message for 2.x, when it finds IE 8.

It is very easy to upgrade jQuery to 2.x and not be aware that there was a conscious choice in the current version to not support 8. This choice is well documented here, but if you are updating through another method (like NuGet from inside MS Visual Studio), there is no loud warning.

jakecigar

Re: Re: issue with 2.1.0 and ie

8 years ago

You can read up on chrome=1. It’s very cool!

JΛ̊KE

Greg Litt..

Re: issue with 2.1.0 and ie

8 years ago

Agreed, Chrome Frame was very cool. According to Google,

But in 2009, many people were using browsers that lagged behind the leading edge. In order to reach the broadest base of users, developers often had to either build multiple versions of their applications or not use the new capabilities at all. We created Chrome Frame — a secure plug-in that brings a modern engine to old versions of Internet Explorer — to allow developers to bring better experiences to more users, even those who were unable to move to a more capable browser.

Today, most people are using modern browsers that support the majority of the latest web technologies. Better yet, the usage of legacy browsers is declining significantly and newer browsers stay up to date automatically, which means the leading edge has become mainstream.

Given these factors we’ve decided to retire Chrome Frame, and will cease support and updates for the product in January 2014.

http://blog.chromium.org/2013/06/retiring-chrome-frame.html

Current status is retired and Google is recommending developers no longer use it.

My sites opt into Chrome Frame with chrome=1 in the X-UA-Compatible meta tag or HTTP header.
If you don't require Chrome Frame to use your content, you can remove these opt-in headers now, and slim down the bytes sent to users.

https://developers.google.com/chrome/chrome-frame/

Back to the real question.

Is this kind of "crash" considered a bug? Or just an unfortunate, but expected side effect of progress.

My current web development project has only in-house clients, so I can "guarantee" that no one will use IE 8. And I now have a "patch" to keep IE 10 from act like IE 8. So, it's jQuery 2.x for me.

But, what about the millions of others (developers and end users) that depend on jQuery, but don't know the root cause of this error yet?

Is there a way to help them?

jakecigar

Re: Re: issue with 2.1.0 and ie

8 years ago

If you use code, you need to protect yourself.

I like to code

<!--[if lt IE 9]>
<script src="http://code.jquery.com/jquery-1.11.0.js"></script>
<![endif]-->
<script src="http://code.jquery.com/jquery-2.1.0.js"></script>

For the occasional bozo who runs IE8.

JΛ̊KE

Greg Litt..

Re: issue with 2.1.0 and ie

8 years ago

The solutions are not complicated. This one is smart enough to correctly deal with both IE 8 and IE 10 in compatibility mode.

Knowing that jQuery properly prides itself on bridging all sorts of messy browser differences,

What in this error message would get a developer thinking

"Upgrading from 1.x to 2.x is the source of my problem."?

Especially when it is crashing in IE 10, which is fully supported in 2.x. I was able to easily find that "addEventListener" was not handled the same in IE as other browsers (thanks MS), so failure to identify the browser was the easy blame. But, that got me no closer to a cause/fix.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Timestamp: Tue, 22 Apr 2014 18:07:03 UTC

Message: Object doesn't support property or method 'addEventListener'
Line: 3398
Char: 4
Code: 0
URI: file:///W:/Temp/jQuery/jquery-2.1.0.js

jakecigar

Re: issue with 2.1.0 and ie

8 years ago

jQuery 1.x prides itself…

jQuery 2.x is leaner because it doesn’t deal with ancient IE.

I doubt the dev team will add extra code to warn IE7 users on jQuery 2.x. You need to do that.

JΛ̊KE

watusiware

Re: issue with 2.1.0 and ie

8 years ago

The download page is pretty clear about it.

Since IE 6/7/8 are still relatively common, we recommend using the 1.x version unless you are certain no IE 6/7/8 users are visiting the site.

jQuery 2.x has the same API as jQuery 1.x

So, jQuery 2.x is an optimization for situations where you can be sure you have a modern browser.

Admittedly, the numbering scheme is a bit odd. It would be clearer if it were, say, jQuery 2.x and jQuery-ng 2.x...

As a practical matter, if you use it on a website today, you need to either use jQuery 1.x or use the simple scheme above to serve the appropriate version to each user.

If you're writing, say, a PhoneGap app for iOS or Android, you can simply use 2.x, because you know for sure the browser is supported.

If this is too much trouble for you, there's nothing wrong with using the latest 1.x. It's functionally identical. It's just a little slower and a little bigger.

Greg Litt..

Re: issue with 2.1.0 and ie

8 years ago

My concern is not poor documentation (except perhaps the sneaky case of IE 10 that is in compatibility mode). My concern is not even for myself (my code now work great, thank you very much). My concern is for the other folks who will get (or have gotten) an error and have no clue why.

Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media
Center PC 6.0; .NET4.0C; .NET4.0E)
Timestamp: Tue, 22 Apr 2014 18:07:03 UTC

Message: Object doesn't support property or method 'addEventListener'
Line: 3398
Char: 4
Code: 0
URI: file:///W:/Temp/jQuery/jquery-2.1.0.js

This clearly tells me 2.x was running when it died, but gets me no closer to getting my code working again.

In my case, I did an "accidental" upgrade from 1.x to 2.x, while I was updating several other packages through a 3rd party, NuGet from inside Visual Studio. If the error had appeared right after the upgrade, in only IE 8 and jQuery was the only thing I had updated. The answer would have been simple enough.

But, I first saw the error a week or so later on a single IE 10, leaving me with hundreds of possible causes.

jakecigar

Re: issue with 2.1.0 and ie

8 years ago

There is nothing jQuery can or will do for detecting this mistake. 2.x is for people who know their audience.

JΛ̊KE

Top Reply

Response title

Attachments

jQuery Forum

issue with 2.1.0 and ie

Replies(12)

Re: issue with 2.1.0 and ie

Re: Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Re: issue with 2.1.0 and ie

Statistics

Tags

Actions