3 ms·

> WHATWG have removed features before, e.g. frameset, font, and applet elements from HTML. font: supported in all browsers https://caniuse.com/?search=font htt

by troupo 1y ago

> WHATWG have removed features before, e.g. frameset, font, and applet elements from HTML. font: supported in all browsers https://caniuse.com/?search=font https://caniuse.com/?search=font frameset: supported in all browsers https://caniuse.com/?search=frameset https://caniuse.com/?search=frameset applet: supported in all browsers https://caniuse.com/?search=applet https://caniuse.com/?search=applet > All of them were rarely used and had better alternatives available. "Rarely used" is not enough of a justification

ioasuncvinvaer 1y ago
So a feature was removed from the spec and it is still supported. I don't see how it would be bad to remove XSLT then?
- mananaysiempre 1y ago
  There’s an explicit deside to unship XSLT on the browsers’ part, from what I understand. That’s what motivated the spec proposal in the first place.
vitus 1y ago
nit: document.applets is not the same as the <applet> tag. Note: Support for the <applet> element has been removed by all browsers. Therefore, calling document.applets always returns an empty collection. https://developer.mozilla.org/en-US/docs/Web/API/Document/applets https://developer.mozilla.org/en-US/docs/Web/API/Document/ap... For instance: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/56 https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel... The <applet> element has been removed (Firefox bug 1279218). Also see https://github.com/mdn/content/pull/26850 https://github.com/mdn/content/pull/26850 which removed MDN docs for the element a couple years back, citing removals from major browsers. <font> and <frameset> are still implemented in browsers, though, even if they are fully deprecated and marked by WHATWG as obsolete and non-conforming: https://html.spec.whatwg.org/multipage/obsolete.html#non-conforming-features https://html.spec.whatwg.org/multipage/obsolete.html#non-con...
- troupo 1y ago
  Thank you for the correction!

by troupo 1y ago

ioasuncvinvaer 1y ago

So a feature was removed from the spec and it is still supported. I don't see how it would be bad to remove XSLT then?

mananaysiempre 1y ago
There’s an explicit deside to unship XSLT on the browsers’ part, from what I understand. That’s what motivated the spec proposal in the first place.

vitus 1y ago

nit: document.applets is not the same as the <applet> tag. Note: Support for the <applet> element has been removed by all browsers. Therefore, calling document.applets always returns an empty collection. https://developer.mozilla.org/en-US/docs/Web/API/Document/applets https://developer.mozilla.org/en-US/docs/Web/API/Document/ap... For instance: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/56 https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel... The <applet> element has been removed (Firefox bug 1279218). Also see https://github.com/mdn/content/pull/26850 https://github.com/mdn/content/pull/26850 which removed MDN docs for the element a couple years back, citing removals from major browsers. <font> and <frameset> are still implemented in browsers, though, even if they are fully deprecated and marked by WHATWG as obsolete and non-conforming: https://html.spec.whatwg.org/multipage/obsolete.html#non-conforming-features https://html.spec.whatwg.org/multipage/obsolete.html#non-con...

troupo 1y ago
Thank you for the correction!