Removing XSLT for a more secure browser
developer.chrome.com
Removing XSLT for a more secure browser
1–10 of 352 posts
Re: Removing XSLT for a more secure browser
#2Destroying the open web instead of advocating to fix one of the better underutilized browser technologies for a more Profitable Google.
I will not forget the name Mason Freed, destroyer of open collaborative technology.
Re: Removing XSLT for a more secure browser
#3"Removing established open standards for a more walled garden" -> Fixed
Re: Removing XSLT for a more secure browser
#4So XPath locators won't be available in Playwright and Selenium in Chrome? This could be huge for QA and RPA.
Re: Removing XSLT for a more secure browser
#5I know it makes me an old and I am biased because one of the systems in my career I am most proud of I designed around XSLT transformations, but this is some real bullshit and a clear case why a private company should not be the de facto arbiter of web standards. Have a legacy system that depends on XSLT in the browser? Sucks to be you, one of our PMs decided the cost-benefit just wasn't there so we scrapped it. Take comfort in the fact our team's velocity bumped up for a few weeks.
And yes I am sour about the fact as an American I have to hope the EU does something about this because I know full-well it's not happening here in The Land of the Free.
Re: Removing XSLT for a more secure browser
#6Good, XSLT was crap. I wrote an RSS feed XSLT template. Worst dev experience ever. No one is/was using XSLT. Removing unused code is a win for browsers. Every anti bloat HNer should be cheering
Re: Removing XSLT for a more secure browser
#7Destroying the open web instead of advocating to fix one of the better underutilized browser technologies for a more Profitable Google. I will not forget the name Mason Freed, destroyer of open collaborative technology.
Didn't this effort start with Mozilla and not Google? I think you will in fact forget the name Mason Freed, just like most of us forgot about XSLT.
Re: Removing XSLT for a more secure browser
#8So XPath locators won't be available in Playwright and Selenium in Chrome? This could be huge for QA and RPA.
They are still keeping the XPath APIs so XPath locators will still work.
Re: Removing XSLT for a more secure browser
#9This has been chewed on ad nauseum on HN already, to the point I won't even try to make a list of the articles but just link a search result: https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=fal...
Re: Removing XSLT for a more secure browser
#10TIL: Chrome supports XSLT.
Good riddance I guess - it and most of the tech from the "XML era" was needlessly overcomplicated.