HTML 5 Draft Standard - 30 July 2009 - Huihoo

34
2.1.3 Scripting
The construction "a Foo object", where Foo is actually an interface, is sometimes used instead of
the more accurate "an object implementing the interface Foo".
A DOM attribute is said to be getting when its value is being retrieved (e.g. by author script),
and is said to be setting when a new value is assigned to it.
If a DOM object is said to be live, then that means that any attributes returning that object must
always return the same object (not a new object each time), and the attributes and methods on
that object must operate on the actual underlying data, not a snapshot of the data.
The terms fire and dispatch are used interchangeably in the context of events, as in the DOM
Events specifications. [DOM3EVENTS]
2.1.4 Plugins
The term plugin is used to mean any content handler for Web content types that are either not
supported by the user agent natively or that do not expose a DOM, which supports rendering the
content as part of the user agent's interface.
Typically such content handlers are provided by third parties.
One example of a plugin would be a PDF viewer that is instantiated in a browsing context
(page 608) when the user navigates to a PDF file. This would count as a plugin regardless
of whether the party that implemented the PDF viewer component was the same as that
which implemented the user agent itself. However, a PDF viewer application that launches
separate from the user agent (as opposed to using the same interface) is not a plugin by
this definition.
Note: This specification does not define a mechanism for interacting with
plugins, as it is expected to be user-agent- and platform-specific. Some UAs
might opt to support a plugin mechanism such as the Netscape Plugin API;
others might use remote content converters or have built-in support for
certain types. [NPAPI]
⚠Warning! Browsers should take extreme care when interacting with external
content intended for plugins (page 34). When third-party software is run with the
same privileges as the user agent itself, vulnerabilities in the third-party software
become as dangerous as those in the user agent.
2.1.5 Character encodings
An ASCII-compatible character encoding is a single-byte or variable-length encoding in
which the bytes 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F, 0x41 - 0x5A,
and 0x61 - 0x7A, ignoring bytes that are the second and later bytes of multibyte sequences, all