Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Multi-select with optgroups causes endless loop in IE 10 for Windows 7 [jqm 1.3] #5695

Closed
avbers opened this Issue · 9 comments
@avbers

Reproduce bug like this:

Go to the jqm 1.3 demo page
http://view.jquerymobile.com/1.3.0/docs/widgets/forms/

Multi-select with optgroups, custom icon and position:click to open
Choose 'Rush'
Click outside page; somewhere in the left margin (not on the select button)

My guess would be that it has something to do with the blur function. This one comes on top while profiling.

My browser is Internet Explorer 10 for Windows 7 Pre-release
Version 10.0.9200.16441

@avbers

Problem persists on Final IE 10 for Windows 7, released today

@avbers avbers closed this
@avbers avbers reopened this
@avbers

Sorry, wrong button

@jaspermdegroot
Collaborator

Just tested this and IE10 completely crashed :/

@ottoville

It does not need optgroups to be crashed, crash without them also.
I also noticed that it does not crash if page is inside iframe element, that is why we do not see bug in jsfiddle.

@ottoville

This is very crusial problem as it causes a pages with selectionmenu to crash in IE, making website totally impossible to visit. I would say fixing this problem should be number one priority.

@asgeo1

A customer for one of my apps has been complaining of IE10 (windows 8) crashing when using a select-menu. I haven't been able to replicate it myself in IE10. But I'm pretty sure this is the issue from what they've described.

I'm also not using optgroups. It's just a standard select-menu. No idea why it would crash the browser...

Would really like to see a fix for this too!

If I could somehow replicate it, I would help fix it. But I've tried the examples people have mentioned, and they seem fine for me in IE10 :-/

@arschmitz arschmitz was assigned
@arschmitz
Owner

Just tested this on browser stack ie10 on windows 7 and i can no longer reproduce since with was reported on a pre-release and there have also been changes to custom select so hard to say which fixed but closing as fixed.

@arschmitz arschmitz closed this
@jaspermdegroot
Collaborator

This was caused by incorrect markup on our demo page. We will clean that up.

@debarupa

This is still not fixed (for version 1.3). In the latest version (jqm 1.4) it works but for our project, migrating to 1.4 messed up the website's look and feel completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.