- priority changed from undecided to low
- status changed from new to open
- type changed from feature to bug
- component changed from unfiled to manipulation
- milestone changed from None to 1.8
I agree this limits the utility of chaining.
The easiest way out would be to remove support for using before/after to add something to an empty set, which was added without a lot of thought for how it might affect these situations and has been a thorn in our side ever since. It seems potentially like quite a breaking change to some code, though.
To fix this specific case, if the div was always stacked you'd end up with the .after adding to an empty set and then being thrown away by the .end, which shouldn't break anything.
