Closed Eiji7 closed 7 years ago
@Eiji7 Good catch! I think this problem extends not only for the sibling selector (">"). It should have the same problem for general sibling ("~") and the "nth-child" pseudo class selector.
I'm looking into fix this soon. Thank you for the report!
For this code:
I run:
Expected results:
Actual results:
Note: With this html:
and this:
find method works as expected.
So problem is that
Floki
interprets
(text node) as normal node. So next element (for Floki) afterspan
element is text node instead ofa
element.Note2: As a workaround I tried:
but I got: