JQuery Mobile 1.0RC2 is currently incompatible with JQuery 1.7 under IE8

[ghost]

Disclaimer: I first posted this issue on the JQuery Mobile forum, but got no answer. I was hesitant to post it here as JQuery 1.7 is still fairly new and Mobile 1.0RC-2 may not be compatible with it just yet. Feel free to dismiss this issue if it's known.

I decided to try out the recently released JQuery 1.7 with JQuery Mobile 1.0RC2 assuming that everything would work out of the box. Everything seems to be fine under Windows 7 with Chrome 15.0.874.106m Safari 5.1.1 and Firefox 7.0.1.

However, I ran into a problem under IE8 on a Windows XP PRO SP3 machine where JQuery 1.7 had an error on load. This is the error message: Can't move focus to the control because it's invisible, not enabled, or of a type that does not accept the focus.

This seems to be related to how the mobile markup is being generated/inserted and JQuery 1.7's "Better Support for HTML5 in IE6/7/8".

Here's a jsfiddle that reproduces the issue. There is no such problem with JQuery 1.6.4.

Thank you.

[johnbender]

@Hdnc

Thanks for testing it out with 1.7, we actually had a relatively lengthy internal discussion about whether to ship 1.0 with 1.7 support. We decided against it and it looks like, at least in this case, we made the right call.

We'll have to discuss the priority on this one but, again, thanks for posting your findings!

[ghost]

@johnbender

Thank you for confirming this. I'm glad that my findings could help the team. In this case, I'll go ahead and close this ticket. Thank you.

[johnbender]

After talking with @dmethvin from the core team there is something odd going on here with the header element in the jsfiddle that is causing it to report offsetWidth > 0 (core's check for visibility) though it should be invisible at that point and ignored. I'll post more info here as I sort it out.

[johnbender]

@laurentboileau

Can you verify this on your end. In my testing with your fiddle it addressed the issue.

[ghost]

I created an html file from my fiddle and the problem persisted under IE8. However applying the code in your commit fixed the issue. The page now renders properly under IE8.

I also tested a more complex project with core 1.7 and everything is running smoothly. If you don't have anything to add you can go ahead and close this issue.

Thank you very much John.