Forwarded message 1
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
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]