.after() breaks on disconnected DOM node with content

[Jack <juichenieder-jq@…>]

Ok, quick description.

This works as expected (it returns a set of 2 dom nodes):
$('<div></div>').after('<p></p>')

This does not work (it returns only the first of the 2 dom nodes):
$('<div>f</div>').after('<p></p>')

[timmywil]

We fixed this issue in closest for 1.6, but there is probably an underlying issue we should take a closer look at. Closing as duplicate.

[timmywil]

Duplicate of #7369.

[Jonas Lundgren]

This is still broken in 1.6.1

[timmywil]

Thanks. Meant to reopen this one.

[timmywil]

​http://jsfiddle.net/timmywil/UQ7NS/

[john]

I think we just need to make sure that the parentNode isn't a document fragment. Confirmed in triage.

[antishok]

I think #10517 is a dupe of this one, and it was fixed in the latest 1.8b2

[dmethvin]

Agreed.

[dmethvin]

Duplicate of #10517.

[leomontenegro6@…]

Strangely, I'm getting the same issue after updating jQuery from 1.8.2 to 1.11.0. The $.after() and $.before() methods aren't working on newly created elements. I need to firstly add the newly created element to DOM, and then insert the new content to it. Dunno if it's a bug, of if these methods were changed.

Anyway, a workaround for this is using $.add() method, but it will work only as a alternative to $.after() method, not $.before().