anupamjain@g... wrote:
> I was converting the HTML to XHTML using JTidy and then parsing it
> using Xerces at the server side.(So it 'was' XHTML on the server side,
> so no TBODYs)
>
> But I guess now I will parse it also on the client side using mozilla's
> doc.evaluate (It's ok  for me if it runs only on Mozilla)
>
> I hope it works. Will let you know.

It will not work - but you may try out of interest. First of all IE
doesn't support XHTML at all - it will be parsed as malformed HTML
Transitional with the most funny results (and the most fancy trees) to
expect. Given the phantom nodes problem on the standard-compliant
company plus some little but nasty DOM parsing discrepancies between
different browsers... I would say your idea of server-side /
client-side matching xpath's is like running two random numbers
generators on two machines and hope that the sequences will match.

I would suggest to use xpath in the environment it was intended to:- in
XSLT templates to process XML data part. With .xml (data) and .xsl
(transformations) you'll get what you want in the cross-browser way.