As of the last couple years, Chrome is the web. The writing has been on the wall since at least Widevine. The browser wars are over, and I don't see any scrappy startup crossing the moat of complexity GOOG has built around "modern" browsers. Especially when combined with their stranglehold of the standards committees. We need to find a new attack vector.
Chrome unlikely to support XPath 3.1
31–40 of 114 posts
Re: Chrome unlikely to support XPath 3.1
#32Safari 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
#33https://bugs.chromium.org/p/chromium/issues/detail?id=514995
which was already nuts, so they are clearly not interested in anything related to XML. XML is a fantastic tool, it's just that a whole generation of developers refused to even touch it and are biased against it.
And since Chrome is now basically the web... wait til there is only Chrome and Safari left and see what happens to web "standards"...
Re: Chrome unlikely to support XPath 3.1
#34Re: Chrome unlikely to support XPath 3.1
#35Safari 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
https://caniuse.com/push-api https://caniuse.com/mediasource
Re: Chrome unlikely to support XPath 3.1
#36Earlier quoted context omitted.
They’ll do it to themselves. One thing I see regularly is Chrome’s web caching being so aggressive it is driving front-end developers to start using FF for dev. We simply need to stand back and let time take its course.
Does Chrome no longer have the option to disable cache while dev tools is open?
Re: Chrome unlikely to support XPath 3.1
#37Safari 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
#38Re: Chrome unlikely to support XPath 3.1
#39i guess the non-inflammatory title would be “representative of chrome project votes no in one of many working group proposals “?
They didn't just vote no. They basically said they're not implementing it even if everyone else votes yes.
Re: Chrome unlikely to support XPath 3.1
#40Safari 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
https://www.zdnet.com/article/apple-declined-to-implement-16...