Bug Tracker


Opened 5 years ago

Closed 4 years ago

#12503 closed bug (fixed)

before/after will choke if collection has not first disconnected node

Reported by: anonymous Owned by:
Priority: low Milestone: 1.9
Component: manipulation Version: git
Keywords: Cc:
Blocked by: Blocking:


Logical fix for this situation would be add new node to DOM before connected node and add new node to collection before disconnected one, but given that this case is rare and will reflect purely on byte size and perfomance, i propose only change DOM and do not change collection.

Change History (4)

comment:1 Changed 5 years ago by dmethvin

  • Component changed from unfiled to manipulation
  • Milestone changed from None to 1.9
  • Priority changed from undecided to low
  • Status changed from new to open

The team is thinking we may just deprecate before/after on disconnected elements, so this behavior would be undefined.

comment:2 Changed 5 years ago by gibson042

Related: #11226 #11230

comment:3 Changed 4 years ago by saiwong

This has been fixed in #12664.

Recommend this ticket be closed.

comment:4 Changed 4 years ago by mikesherov

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

fixed in #12664.

Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Modify Ticket

Change Properties

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.