The HTML Elements Time Forgot

35 points by carlana


oneirine

<plaintext> is a funny one. It does what it says on the tin – that is, tells the browser to interpret everything after it as plain text. Of course, this means that any potential closing tag is also interpreted as plain text and therefore not parsed by the browser. Once opened, you cannot close a <plaintext>. The rest of the file becomes plaintext for eternity and whatever comes after.

That's wonderfully cursed. I love it.

As for the bit about <spacer> and spacer gifs, worth mentioning that spacer-like approaches have come back into fashion somewhat in frontend webdev in the last few years, for better or worse.

ianloic

So much of my early web app development was perl4 and <isindex>. Good times....

lorddimwit

And the beast shall come forth surrounded by a roiling cloud of vengeance. The house of the unbelievers shall be razed and they shall be scorched to the earth. Their tags shall blink until the end of days.

scruss

Oh NEXTID ... back in the days when everyone (well, okay, people in standards bodies who'd been around groups like the Text Encoding Initiative) expected web pages to have unique, persistent name anchors down to paragraph level (at least), sentence level (getting there) or even word level (galaxy mind enabled). What's more, you were expected to be able to deep-link into anyone's page who had them. Of course.

It was round about that time that I saw an entirely serious proposal that all web pages should encode text complete with soft hyphenation entities (&shy;) embedded in words. Forget accessibility and editability, we have nice smooth right margins!