[webkit-dev] XPath Issues?

[Alexey Proskuryakov]

03.11.2010, в 9:38, Alex Milowski написал(а):

> https://bugs.webkit.org/show_bug.cgi?id=26157

This is a request to implement an optimization, and one that doesn't seem particularly likely to provide material benefits. The optimization has an observable effect of reusing the same object though.

> https://bugs.webkit.org/show_bug.cgi?id=12504

Namespace nodes are pure evil, we shouldn't do that.

> https://bugs.webkit.org/show_bug.cgi?id=13233

This is a place to track future optimization ideas and performance tests.

> https://bugs.webkit.org/show_bug.cgi?id=12632

This is correct behavior, but Firefox has a bug. We could match Firefox, but with no actual sites known to be affected that doesn't seem important.

> https://bugs.webkit.org/show_bug.cgi?id=12496

An optimization opportunity.

> https://bugs.webkit.org/show_bug.cgi?id=36427

Unspecified behavior, different from Firefox.

> Anything else out there?  Is it complete?  I'm curious about how
> robust this implementation is and what enhancements have been filed
> for it.

I think that the only actual bug we have was not on the list, <https://bugs.webkit.org/show_bug.cgi?id=34231>. JS wrappers should be preserved for all reachable nodes, which includes nodes in XPath result sets.

> I'm also looking at what it would take to enhance this implementation
> to support XPath 2.0 ...

XPath 2.0 is not fully compatible with 1.0. JavaScript API for XPath doesn't provide a way to choose version - at least, it didn't when I last checked. So, we can't really support 2.0.

- WBR, Alexey Proskuryakov