> This has to be proven by Google (and other browser vendors), not by people coming up with examples

What, to you, would constitute sufficient proof? Is it feasible to gather the evidence your suggestion would require?

> What, to you, would constitute sufficient proof? Is it feasible to gather the evidence your suggestion would require?

Let me quote from my comment, again:

--- start quote ---

The guy pushing "intent to deprecate" didn't even know about the most popular current usage (displaying podcast RSS feeds) until after posting the issue and until after people started posting examples

--- end quote ---

I would like to see more evidence than "we couldn't care less, remove it" before a consensus on removal, before an "intent to deprecate" and before opening a PR to Chrome removing the feature.

Funnily enough, even the "browser consensus" looks like this: "WebKit is cautiously supportive. We'd probably wait for one implementation to fully remove support": https://github.com/whatwg/html/issues/11523#issuecomment-314...

BTW. Literally the only "evidence" originally presented was "nearly 100% of sites use JS, while 1/10000 of those use XSLT.": https://github.com/whatwg/html/issues/11523#issuecomment-315... which was immediately called into question: https://github.com/whatwg/html/issues/11523#issuecomment-315... and https://github.com/whatwg/html/issues/11523#issuecomment-315... and that's before we account for google's own docs saying they have a blind spot in the enterprise/corporate setting where people suspect the usage may be higher.

Also, as I say. I think the main issue isn't XSLT itself. XSLT is a symptom.