Skip to main content

Bug Tracker

Side navigation

#14190 closed bug (fixed)

Opened July 26, 2013 03:45PM UTC

Closed July 26, 2013 05:35PM UTC

Last modified November 06, 2013 03:37PM UTC

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:

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 and reverting to the version of

from 1.9.1 fixes the problem.

Attachments (0)
Change History (11)

Changed July 26, 2013 04:47PM UTC by dmethvin comment:1

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:

Changed July 26, 2013 05:03PM UTC by dmethvin comment:2

status: newopen

Changed July 26, 2013 05:35PM UTC by dmethvin comment:3

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.

Changed July 30, 2013 07:03AM UTC by anonymous comment:4

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


Changed July 30, 2013 01:09PM UTC by dmethvin comment:5

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

Changed August 29, 2013 11:34PM UTC by comment:6

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. :-)

Changed August 30, 2013 12:30AM UTC by dmethvin comment:7

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.

Changed October 20, 2013 02:23AM UTC by anonymous comment:8

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.

Changed October 21, 2013 12:28PM UTC by tj.vantoll comment:9

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

Changed October 28, 2013 02:44PM UTC by anonymous comment:10

I also could reproduce this in:

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. (

Pleas have a look and maybe merge this?


Changed November 06, 2013 03:37PM UTC by Marian Sollmann comment:11

resolution: notabugfixed

Fix #14190: Remove unnecessary assignment in .closest. Close gh-1411.

(cherry picked from commit 346b031af9e3b315ef351a9cc7fee56f930cf346)



Changeset: ff365d305fc22f40f4df9c4a6c7b1ca6c3c9800d