-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE8 x-ua compatible mess #1
Comments
Can you set up a test page where an error occurs? I can't actually replicate the issue (even though everything I've read suggest it shouldn't work)! |
Ok those urls should do it :
only document.documentMode will give you the appropriate version (you can test it in the js console of ie developper tools) Be carreful because as soon as you activate compatibility mode by hand, it will always work as you expect ("7.0") |
I've just released v1.1, can you try it and see if the problem is resolved? |
Works perfectly thanks good work ! |
Hello, dunno if this is a jquery bug or jquery onhashchange bug, i'll explain :
when a user activates compatibility mode in IE8 (so manual modification), jQuery.browser.version do report "7.0".
but if the website force ie7 mode (with meta http-equiv="X-UA.. content="IE=EmulateIE7), jQuery will report "8.0"
As you can see, the code from jquery-hashchange will fail here if the website uses the meta way. Because it'll try to use native onhashchange event wich will not be available when emulating ie7.
I know jQuery doesn't want to make fancy things on jQuery.browser, that's why i'm adressing the bug to jquery-hashchange
There's an easy workaround, just test document.documentMode wich will report good versions in both cases : "7.0" when the browser is in compatibility mode (manual way) or forced by a meta. Also it will report 8.0 if in normal mode
What do you think ?
source : http://msdn.microsoft.com/en-us/library/cc288325%28VS.85%29.aspx
The text was updated successfully, but these errors were encountered: