At 08:33 AM 6/24/2003 -0700, you wrote:
Richard Kunze
<kunze@xxxxxxxxx> writes:
> > but if the former, then this change would be very, very nice to
have.
>
> Lets put it on the agenda for XMLC 3.0. A new DOM implementation is
pretty
> much a given for XMLC 3.0 anyway, so we can just as well include
case
> insensitive XPath support for HTML.
Guys, this will break tons of code and it will no longer be W3C
HTML
compatiable DOM. This is a either a bug or missing feature in
XPath, depending on your point of view... Submit a patch to em, the
logic
for checking for an HTML doc is easy:
if (node.getDocument() instanceof
org.w3c.dom.html.HTMLDocument) {
.....
}
Agreed. I'll ask the guys at Jaxen (used in DOM4j and elsewhere)
and JXPath what their take on this issue is. The XPath engine is
probably where the case-sensitivity issues should be addressed rather
than storing a non-standard DOM.
Jake
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 