Fun fact: this is very close but slightly inaccurate. I used to think this is how it worked before scrutinizing a rule in the HTML tree-building specification.

Fun fact: this is very close but slightly inaccurate. I used to think this is how it worked before scrutinizing a rule in the HTML tree-building specification. The tag leads the parser to interpret everything following it as character data, but doesn’t impact rendering. In these cases, if there are active formatting elements that would normally be reconstructed, they will after the PLAINTEXT tag as well. It’s quite unexpected. <a href="https://news.ycombinator.com"><b><i><u><s><plaintext>hi In this example “hi” will render with every one of the preceding formats applied. https://software.hixie.ch/utilities/js/live-dom-viewer/?%3Ca%20href%3D%22https%3A%2F%2Fnews.ycombinator.com%22%3E%3Cb%3E%3Ci%3E%3Cu%3E%3Cs%3E%3Cplaintext%3Ehi https://software.hixie.ch/utilities/js/live-dom-viewer/?%3Ca... After I discovered this the note in the spec was updated to make it clearer. https://html.spec.whatwg.org/multipage/parsing.html#:~:text=A start tag whose tag name is "plaintext"