4 ms·
It also rejected one of my favorites, the long-deprecated <xmp>
by jefftk 2y ago
It also rejected one of my favorites, the long-deprecated <xmp>
- myfonj 2y ago<xmp> and <plaintext> never die! I think/hope/believe that even though these elements fell out of grace of the standard bodies [1] long time ago, implementers simply cannot go against backwards compatibility here and remove them like spec suggest and MDN scaremongers that it "was not implemented in a consistent way" [2], yet last time I checked, the support in major browsers was pretty solid [3]. - [1] yet https://html.spec.whatwg.org/multipage/obsolete.html#xmp https://html.spec.whatwg.org/multipage/obsolete.html#xmp tells still acknowledges that "User agents must treat xmp elements in a manner equivalent to pre elements in terms of semantics and for purposes of rendering. (The parser has special behavior for this element though.)" - [2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xmp https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xm... - [3] https://github.com/mdn/browser-compat-data/issues/2168#issuecomment-393708922 https://github.com/mdn/browser-compat-data/issues/2168#issue...
- jefftk 2y agoI do actually use <xmp> when authoring blog posts, though I wrote a preprocessor to convert to escaped <pre> in case some rendering environments don't support it: https://www.jefftk.com/p/i-want-xmp-but-i-know-why-i-cant-have-it https://www.jefftk.com/p/i-want-xmp-but-i-know-why-i-cant-ha...