Bug Tracker

Ticket #9905 (closed bug: fixed)

Opened 4 years ago

Last modified 3 years ago

.removeAttr( "id" ) sometimes crashes IE 7

Reported by: scott.gonzalez Owned by:
Priority: high Milestone: 1.9
Component: attributes Version: 1.6.2
Keywords: ie7 Cc:
Blocking: Blocked by:


I can't really describe this any better than the raw code from the test case does but...

If you clone an element and then call .removeAttr( "id" ) everything is fine. If you repeat the cloning and removal of the attribute, everything is still fine. However, if you first query for one of its ancestors, and then query from there for a descendant, IE 7 will crash.

I haven't attempted to reduce this any further, e.g., querying for a non-existent descendant, or querying by something other than id.

This exists in 1.6.x and master and seems to only affect IE 7 (even IE 6 is fine).

Test case:  http://jsfiddle.net/r6zFU/1/

Change History

comment:1 Changed 4 years ago by scott.gonzalez

jQuery UI ticket with workaround:  http://bugs.jqueryui.com/ticket/7538

comment:2 Changed 4 years ago by timmywil

  • Priority changed from undecided to high
  • Component changed from unfiled to attributes
  • Milestone changed from None to 1.next

That's strange.

comment:3 Changed 4 years ago by timmywil

  • Status changed from new to open

comment:4 Changed 4 years ago by francis@…

Thank goodness somebody else has found this as I was thinking I was going crazy. I definitely can repeat this:

options.templates.tabs = options.tabsTemplateRoot.clone()
alert('clone complete');
alert('class removed');
alert('id removed');

On second time around Internet Explorer 7 only gets to "alert class removed" and then crashes. At least for the moment we can work around.

comment:5 Changed 4 years ago by dmethvin

  • Keywords ie7 added

I suspect this is related to #9646.

comment:6 Changed 3 years ago by gibson042

  • Milestone changed from 1.next to 1.9

Batch update of oldIE bugs to milestone 1.9 for resolution/reevaluation/closing/etc.

comment:7 Changed 3 years ago by dmethvin

  • Status changed from open to closed
  • Resolution set to fixed

Fixed with the commit for #9646.

Note: See TracTickets for help on using tickets.