Bug Tracker

Modify ↓

Ticket #12503 (closed bug: fixed)

Opened 8 months ago

Last modified 7 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:

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

comment:1 Changed 8 months 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 8 months ago by gibson042

Related: #11226 #11230

comment:3 Changed 7 months ago by saiwong

This has been fixed in #12664.

Recommend this ticket be closed.

comment:4 Changed 7 months ago by mikesherov

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

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.

View ↑

Add a comment

Modify Ticket

Action
as closed
Author


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

Attachments ↑
 
Note: See TracTickets for help on using tickets.