DO NOT COMPLY.
-
DO NOT COMPLY.
#Google is moving forward with its removal of #XSLT support instead of fixing their library and/or adopting a library that supports a more modern version of the XSLT standard.
The dishonest and incomplete reporting on their developer page omits any explanation on why they have not pursued the corect course of action, and is instead dumping on users and developers the task of compensating for the Chrome team choices:
https://developer.chrome.com/docs/web-platform/deprecating-xslt
DO NOT COMPLY.
-
This is a trillion-dollar company abusing their power to control the open web, and one it's catastrophic how even among the purported supporters of an open web there are people stanning for this choice because of their personal dislike of the piece of tech being forcefully obsoleted on false and flimsy premises.
A reminder that I recently wrote up a historical review on Google's efforts in this direction
-
Do not install the polyfill. Do not change your XML files to load it. Instead, flood their issue tracker with requests to bring back in-browser XSLT support. Report failed support for XSLT as a broken in browsers, because this is not a website issue.
-
G gustavinobevilacqua@mastodon.cisti.org shared this topic
-
Note that the #Chrome team could trivially ship the polyfill itself and nobody would have even _cared_ about the change in the way #XSLT support was implemented in browser. This would have completely solved the “security” issue due to #Google leeching on a #FLOSS libraries without giving back. The fact that they haven't shows that the security issues in the libraries are just an excuse.
Any comment on this, @drott ?
-
There's an older parallel here for when #Mozilla helped #Google in their path to kill #RSS (note that this #XSLT is *also* about that) by removing the Live Bookmark feature. At the time, the excuse was that the implementation was incompatible with some important code changes that were happening at the same time, but the fact that support could be trivially brought in via extension showed that the issue there wasn't technical, but a matter of intent.
-
#Chrome's deprecation of #XSLT is just the next step in the decade-long efforts by #Google to kill an open, independent web (reminder that I've collected some of that history here <https://wok.oblomov.eu/tecnologia/google-killing-open-web/>). The #WebKit developers at #Apple or the prone #Mozilla developers agreeing on this choice detracts nothing from the argument.
-
#Apple is no better than #Google at stewarding the #openWeb. #Mozilla has abundantly shown in the last years that they are just controlled opposition, and the amount of their allegedly restricted resources they waste on invasive features nobody wants shows that they can't be trusted in any way to defend the users' interest. Currently, their only redeeming quality is that they haven't removed support for uBlock Origin and other #adblockers from their browsers —a meager point.
