Re:Chrome unlikely to support XPath 3.1
by londons_explore on Monday November 02, 2020 @02:24AM
(#24965481)
If only a tiny proportion of page views use XPath, it would seem it isn't performance critical.
If that's the case, rewrite the whole lot into JavaScript, run it in the browser sandbox, and rip out the libxml that has security concerns. Then invite pull requests to add new versions of whatwg things.
As soon as a browser API is written in JavaScript and only using other public API's, it becomes a near zero maintenance burden.
If that's the case, rewrite the whole lot into JavaScript, run it in the browser sandbox, and rip out the libxml that has security concerns. Then invite pull requests to add new versions of whatwg things.
As soon as a browser API is written in JavaScript and only using other public API's, it becomes a near zero maintenance burden.