W3C

HTML 5

A vocabulary and associated APIs for HTML and XHTML

← 10 Rendering – Table of contents – 12 Things that you can't do with this specification because they are better handled using other technologies that are further described herein →

11 Obsolete features

Authors and documents must not use the features listed in this section. They are documented to enable user agents to support legacy content in an interoperable fashion.

11.1 Self-contained features

11.1.1 The applet element

The applet element is a Java-specific variant of the embed element. In HTML5 the applet element is obsoleted so that all extension frameworks (Java, .NET, Flash, etc) are handled in a consistent manner.

If the sandboxed plugins browsing context flag is set on the browsing context for which the applet element's document is the active document, then the element must be ignored (it represents nothing).

Otherwise, define how the element works, if supported.

[XXX] interface HTMLDocument {
  readonly attribute HTMLCollection applets;
};

The applets attribute must return an HTMLCollection rooted at the Document node, whose filter matches only applet elements.

11.1.2 The marquee element

...

11.2 Other elements and attributes

The following elements are obsolete and either have no meaning whatsoever or have no requirements beyond those described elsewhere in this specification:

The following attributes are obsolete and either have no meaning whatsoever or have no requirements beyond those described elsewhere in this specification:

11.3 Other DOM APIs

These APIs expose obsolete content attributes.

The [XXX] below is for some annotation meaning "this is just another part of the named interface, and should be treated as if it had been part of the main interface definition".

[XXX] interface HTMLBodyElement {
           attribute DOMString text;
           attribute DOMString bgColor;
           attribute DOMString background;
           attribute DOMString link;
           attribute DOMString vLink;
           attribute DOMString aLink;
};

The text DOM attribute of the body element must reflect the element's text content attribute.

The bgColor DOM attribute of the body element must reflect the element's bgcolor content attribute.

The background DOM attribute of the body element must reflect the element's background content attribute.

The link DOM attribute of the body element must reflect the element's link content attribute.

The aLink DOM attribute of the body element must reflect the element's alink content attribute.

The vLink DOM attribute of the body element must reflect the element's vlink content attribute.

[XXX] interface HTMLDocument {
           attribute DOMString fgColor;
           attribute DOMString bgColor;
           attribute DOMString linkColor;
           attribute DOMString vlinkColor;
           attribute DOMString alinkColor;
};

The fgColor attribute on the Document object must reflect the text attribute on the body element.

The bgColor attribute on the Document object must reflect the bgcolor attribute on the body element.

The linkColor attribute on the Document object must reflect the link attribute on the body element.

The vLinkColor attribute on the Document object must reflect the vlink attribute on the body element.

The aLinkColor attribute on the Document object must reflect the alink attribute on the body element.

11.4 Conformance checkers

To ease the transition from HTML4 Transitional documents to the language defined in this specification, conformance checkers are encouraged to categorise errors that represent usage of old obsolete features that generally have no effect (as defined below) into a separate part of their report, to allow authors to distinguish between likely mistakes and mere vestigial markup.

The following errors may be categorised as described above: