Bug Tracker

Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#14190 closed bug (fixed)

closest fails sporadically in IE11 on Windows 8.1

Reported by: tj.vantoll Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.10.2
Keywords: Cc:
Blocked by: Blocking:


Test case: http://jsfiddle.net/tj_vantoll/kQpVk/.

This is an odd one. In my testing it only occurs in IE11 on Windows 8.1, not Windows 7. You might have to refresh a few times to see the bug as well.

This came from UI bug #9434.

Per the author of the UI bug this is a regression caused by http://bugs.jquery.com/ticket/13332 and reverting to the version of closest from 1.9.1 fixes the problem.

Change History (11)

comment:1 Changed 10 years ago by dmethvin

Hoo boy, this is a heisenbug. If I open the F12 tools and run the example, it always succeeds. So it's kind of hard to debug. Filed as an IE11 bug here:


comment:2 Changed 10 years ago by dmethvin

Status: newopen

comment:3 Changed 10 years ago by dmethvin

Resolution: notabug
Status: openclosed

OK, heard back from Microsoft on this; it's been fixed and not in IE11/Win7. An update for IE11/Win8.1 should be available soon.

Closing as notabug for lack of a better status (we aren't changing anything in jQuery), and since this is a beta.

comment:4 Changed 10 years ago by anonymous

To debug the jsFiddle mashup...

F12>Debug tab>click the Close button dropdown and select "Break on all exceptions"

Press the jsFiddle Run button to rerun the iframe scripts.

you should get

Syntax Error - ln: 1639 in the jQuery module. Opera 10-11 does not throw on post-comma invalid pseudos div.querySelectorAll(“*,:x”);

comment:5 Changed 10 years ago by dmethvin

@anonymous, I am pretty sure that is not related. The case discussed here is not throwing exceptions, it simply had the wrong outcome.

comment:6 Changed 9 years ago by [email protected]

I'm hitting this issue still on IE11 on Windows 8.1... super hard to debug (because, as noted earlier, it disappears if you open the IE11 debugger). Was there anything more specific from Microsoft about when the supposed update will be released? The connect issue that's linked above has been closed as not reproducible. :-)

comment:7 Changed 9 years ago by dmethvin

Probably not repro on the current version. Final IE11 code is supposedly done so just wait until it arrives and check it then. There isn't anything jQuery can do.

comment:8 in reply to:  7 Changed 9 years ago by anonymous

I have the same issue on IE11 under windows 7, I Tabs work a few times and then die. If you press f12 they come back to life.

comment:9 Changed 9 years ago by tj.vantoll

I verified that this is indeed fixed on IE11 in Windows 8.1.

comment:10 Changed 9 years ago by anonymous

I also could reproduce this in: http://jsfiddle.net/akNQj/2/

Just open the jsfiddle in IE11 without the debug console. If you press the "click me" button multiple times. You will get a output if it fails.

I created a push-request on github to solve this. (https://github.com/jquery/jquery/pull/1411) Pleas have a look and maybe merge this?


comment:11 Changed 9 years ago by Marian Sollmann

Resolution: notabugfixed

Fix #14190: Remove unnecessary assignment in .closest. Close gh-1411. (cherry picked from commit 346b031af9e3b315ef351a9cc7fee56f930cf346)



Changeset: ff365d305fc22f40f4df9c4a6c7b1ca6c3c9800d

Note: See TracTickets for help on using tickets.