Bug Tracker

Ticket #12503 (closed bug: fixed)

Opened 2 years ago

Last modified 22 months ago

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:
Blocking: Blocked by:


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

comment:1 Changed 2 years ago by dmethvin

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

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

comment:2 Changed 2 years ago by gibson042

Related: #11226 #11230

comment:3 Changed 22 months ago by saiwong

This has been fixed in #12664.

Recommend this ticket be closed.

comment:4 Changed 22 months ago by mikesherov

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

fixed in #12664.

Note: See TracTickets for help on using tickets.