Skip to main content

Bug Tracker

Side navigation

#11340 closed bug (invalid)

Opened February 13, 2012 09:36PM UTC

Closed February 28, 2012 08:30AM UTC

IE does not understand LEGEND tags

Reported by: SineSwiper Owned by: SineSwiper
Priority: low Milestone: None
Component: manipulation Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:

This works in Firefox, but IE8.0 is choking on the following code in jQuery:

prepend: function() {
   return this.domManip(arguments, true, function( elem ) {
      if ( this.nodeType === 1 ) {
         this.insertBefore( elem, this.firstChild );

With the this.insertBefore statement, IE errors with "Unexpected call to method or property access". As I understand it, IE does this if you try to, say, insert a DOM child element in a non-container (like IMG). The variables are:

elem = SPAN DOM object
this = LEGEND DOM object (with a type of DispHTMLUnknownElement)
this.firstChild = null
this.nodeType = 1

The prime suspect here seems to be the LEGEND tag, as it looks like IE doesn't actually understand what it is, so it calls it "DispHTMLUnknownElement". If it doesn't know what it is, it may not know that it's a container.

Attachments (0)
Change History (2)

Changed February 13, 2012 09:45PM UTC by timmywil comment:1

component: unfiledmanipulation
owner: → SineSwiper
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: Open the link and click to "Fork" (in the top menu) to get started.

Changed February 28, 2012 08:30AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!