Ticket #4391 (closed bug: invalid)
:has() selector is inconsistent when used with element created by .after()
|Reported by:||beaugunderson||Owned by:||john|
Attached is a reproduction that shows the problem in Chrome, IE7, and FF 3.1b3 in my testing.
The reproduction involves adding a list item containing an anchor to the page and then using .next("has:(a)") from a previous sibling to select that element.
It seems to work when .next() is used on the same node that .after() was, but not in the case where .next() is used several siblings before the node that .after() was used on. In that case, the element is not selected.
If this is expected behavior when using .after() to add nodes to the page then I think this is still a valid bug, but in that case only a documentation bug. :)