plain-site › museum
Obsolete elements fall into two groups. The living fossils are out of the spec for authors, but the spec still tells browsers how to render them, so every engine does. The dead were never in a spec or were removed from the engines. Browsers now treat them as unknown elements with no effect. Know which is which.
Netscape's rival to <blink>, from Internet Explorer 2. It is still
supported in Chrome, Firefox and Safari, as HTMLMarqueeElement, with
behavior (scroll / slide / alternate),
direction, scrollamount (px per step), scrolldelay,
loop, bgcolor, width, height, and
start() / stop() methods.
※ Moving text that runs for more than five seconds must have a way to pause it (WCAG 2.2.2). Use it as a joke, or give it a stop button. Never use it for anything a reader needs.
Frames still work in every browser. A <frameset> replaces the
<body> and splits the window into separately scrolling documents. A link
with target loads into a named frame. Open the frames
demo (a whole window), or play with it below.
※ Why frames died: the address bar shows the frameset, not the page you are reading, so links, bookmarks and the back button stop meaning what people expect. A trap. Admire it.
The parser treats everything after <plaintext> as raw text, to the end of
the file. There is no closing tag: the parser never leaves that state. (This demo is safe
because it runs in its own frame.)
A parser quirk: the HTML parser rewrites <image> to
<img> as it reads, because enough 1990s pages wrote it. Inspect the
result: the DOM holds an IMG.
None of these does anything in a current browser. Each line below should look plain. Don't use them: they are not obsolete-but-working, they are gone.
※ Checked in Chrome 155: blink, spacer, multicol and
layer parse as HTMLUnknownElement, and basefont changes
nothing. Open the probe in any browser to check it there.
▲ top ・ plain-site ・ previous: native ・ next: night mode