Hi

I found two possible problems with :eq().
(I haven't tried :gt() and :lt() but they may have the same problems)

Problem 1. The indexing starts at 0 not at 1 as it should be according
to the latest specification.

Problem 2. Using :eq(1) anywhere in a chain collapses the whole tree
to a single thread. For example if I have a tree with many nodes and
branches with one possible node expressed as

XPATH: div[3]/div/table/tbody/tr[2]/td[3]/table/tbody/tr[2]/td/a

If i do not use :eq() as in

       div>div>table>tbody>tr>td>table>tbody>tr>td>a

then I get the whole set of threads which I can look at with .each for
example.

If I use :eq(1) on the last tr as in

       div>div>table>tbody>tr>td>table>tbody>tr:eq(1)>td>a

then whole tree collapses to a single thread equivalent to

div:eq(0)>div:eq(0)>table:eq(0)>tbody:eq(0)>tr:eq(0)>td:eq(0)>table:eq(0)>tbody:eq(0)>tr:eq(1)>td:eq(0)>a

Am I the first to see this? Could someone please confirm that this is
a problem. Sould it be communicated to the developers?

George

Reply via email to