Chrome unlikely to support XPath 3.1

Re:Chrome unlikely to support XPath 3.1 by halflings on Sunday November 01, 2020 @01:01PM (#24961222)

> does not make any reference to costs or benefits to other users of the web platform

> arguments for are being presented publicly in that thread while those against are being discussed elsewhere (perhaps at Google?)

It's right there at the end of the highlighted comment:

"we would love to [...] replace them with something that generates less security bugs. Increasing the capabilities of XML in the browser runs counter to that goal."

So security bugs in XML seems to be the main issue?

[ Parent | on HN ]

Re:Chrome unlikely to support XPath 3.1 by richx on Sunday November 01, 2020 @02:14PM (#24961716)

I’m wondering which security risks they mean. I don’t see any security risk in XML itself, maybe it’s related to some XPath or XQuery functions?

[ Parent | on HN ]

Re:Chrome unlikely to support XPath 3.1 by barefootliam on Sunday November 01, 2020 @02:57PM (#24962019)

I think more about the fact libxml and libxslt are large pieces of code and have had CVEs raised against them (and fixed) in the past. They are still actively maintained.

[ Parent | on HN ]

Re:Chrome unlikely to support XPath 3.1 by foota on Sunday November 01, 2020 @03:01PM (#24962040)

I think the idea is the increased security risk of potentially poorly maintained large body of code with a wide surface area.

[ Parent | on HN ]