Chrome unlikely to support XPath 3.1
github.com
Chrome unlikely to support XPath 3.1
1–10 of 114 posts
Re: Chrome unlikely to support XPath 3.1
#2[deleted]
Re: Chrome unlikely to support XPath 3.1
#3Safari tends to be slow to implement features, but they rarely outright reject implementing a feature.
Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml
Re: Chrome unlikely to support XPath 3.1
#4XML is undeniably a huge attack vector with a shrinking user base. I think that’s a very valid argument for not expanding its surface area.
Re: Chrome unlikely to support XPath 3.1
#5Let’s deprecate old technologies that are currently bundled in web browsers instead of adding to them. Browsers need to go on a diet.
Re: Chrome unlikely to support XPath 3.1
#6Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml
The MathML support in Firefox and Safari are barely usable. Even if my target audience all browsed on Firefox and Safari, I'd avoid MathML.
Re: Chrome unlikely to support XPath 3.1
#7The Google team is right. It had a great run, but it's time to let XML die.
Re: Chrome unlikely to support XPath 3.1
#8Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml
[deleted]
Re: Chrome unlikely to support XPath 3.1
#9This is an editorialized link name and the target comment isn't even obviously wrong or anything. Let the awfully outdated XML tooling die.
Context: This was named "Chrome holding the web back: an example", I expect moderation will change this at some point to something like "Chrome unlikely to support XPath 3.1" which is considerably less incendiary and something few people here care about.
Re: Chrome unlikely to support XPath 3.1
#10The Google team is right. It had a great run, but it's time to let XML die.
Have they proposed an alternative?