Comment by throw7

My jotted down notes:

1. all major vendors (google, mozilla, webkit) want to remove xslt

2. chrome does not have resources to support xslt

3. removing/disabling xslt will be a slow methodical process. don't panic.

4. when opening a proposal change, a pull request of code changes is mandatory to show exact changes; it is not a "countdown to merge"(sic)

5. info that leaks to the public should include context or links to full context

6. removing xslt support in browsers is not good or bad, but "it depends"