I fully support you. Now, getting rid of obsolete, and dead APIs, and features is way more important than adding new ones. I can recall a dozen of XSLT impleme

I fully support you. Now, getting rid of obsolete, and dead APIs, and features is way more important than adding new ones. I can recall a dozen of XSLT implementation bugs which were in Chrome from day 1. XSLT is not going anywhere from browsers, but they also cannot be fixed, because there is so few people using XSLT today to raise above the noise floor for WebKit devs.