Bug Tracker

Opened 11 years ago

Closed 10 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:

Description

​Example
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 11 years ago by dmethvin

Component: unfiled → manipulation
Milestone: None → 1.9
Priority: undecided → low
Status: new → open

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

comment:2 Changed 11 years ago by gibson042

Related: #11226 #11230

comment:3 Changed 10 years ago by saiwong

This has been fixed in #12664.

Recommend this ticket be closed.

comment:4 Changed 10 years ago by mikesherov

Resolution: → fixed
Status: open → closed

fixed in #12664.

Note: See TracTickets for help on using tickets.