Skip to main content

Bug Tracker

Side navigation

#12503 closed bug (fixed)

Opened September 10, 2012 06:16PM UTC

Closed October 22, 2012 04:06PM UTC

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.

Attachments (0)
Change History (4)

Changed September 14, 2012 12:22AM UTC by dmethvin comment:1

component: unfiledmanipulation
milestone: None1.9
priority: undecidedlow
status: newopen

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

Changed September 17, 2012 06:00PM UTC by gibson042 comment:2

Related: #11226 #11230

Changed October 22, 2012 03:31PM UTC by saiwong comment:3

This has been fixed in #12664.

Recommend this ticket be closed.

Changed October 22, 2012 04:06PM UTC by mikesherov comment:4

resolution: → fixed
status: openclosed

fixed in #12664.