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: |
Description
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.
The team is thinking we may just deprecate before/after on disconnected elements, so this behavior would be undefined.