Subject: [xsl] Chrome/blink developers discussing removing XSLT support From: Chris Maloney <voldrani@xxxxxxxxx> Date: Wed, 24 Apr 2013 10:12:50 -0400 |
A friend of mine just sent this out this morning, and I thought it might be of interest to some people on this group. ---- This thread within the "blink-dev" discussion for Chrome's new rendering engine ... examines the possibility of removing support for XSLT from the browser. If so, Blink would be the first major browser to remove support: (https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/KZ0eaL-3vQY) There is some discussion of usage on the web at large, but note Eric Seidel's (of the Chrome team) comment from 4/23: "My suspicion is that neither can be removed from the platform at this time. But both are probably good opportunities for later removal or replacement with JS-based polyfills. I expect removing the need to ship libxslt as part of Chrome to be a small (but non-trivial) binary size win." (https://groups.google.com/a/chromium.org/d/msg/blink-dev/KZ0eaL-3vQY/6Yh4qSidA6AJ) ---- Perhaps if some people here know some resources to determine usage of XSLT on the client, and/or compelling reasons to keep this functionality, they could weigh in. Chris Maloney
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Namespace for reconstitut, David Carlisle | Thread | RE: [xsl] Chrome/blink developers d, Scott Trenda |
Re: [xsl] Namespace for reconstitut, David Carlisle | Date | RE: [xsl] Chrome/blink developers d, Scott Trenda |
Month |