Ticket #12503 (closed bug: fixed)
before/after will choke if collection has not first disconnected node
|Reported by:||anonymous||Owned 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.
- 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