- From: poot <cvsmail@w3.org>
- Date: Thu, 24 Jul 2008 16:15:47 +0900 (JST)
- To: public-html-diffs@w3.org
Add a typographic conventions section; move the terminology section up
and split it into subsections. (whatwg r1919)
Conformance checkers must verify that a document conforms to the applicable conformance criteria described in this specification. Automated conformance checkers are exempt from detecting errors that require interpretation of the author's intent (for example, while a document is non-conforming if the content of a blockquote element is not a quote, conformance checkers running without the input of human judgement do not have to check that blockquote elements only contain quoted material). Conformance checkers must check that the input document conforms when parsed without a browsing context (meaning that no scripts are run, and that the parser's scripting flag is disabled), and should also check that the input document conforms when parsed with a browsing context in which scripts execute, and that the scripts never cause non-conforming states to occur other than transiently during script execution itself. (This is only a "SHOULD" and not a "MUST" requirement because it has been proven to be impossible. [HALTIGPROBLEM]) The term "HTML5 validator" can be used to refer to a conformance checker that itself conforms to the applicable requirements of this specification. XML DTDs cannot express all the conformance requirements of this specification. Therefore, a validating XML processor and a DTD cannot constitute a conformance checker. Also, since neither of the two authoring formats defined in this specification are applications of SGML, a validating SGML system cannot constitute a conformance checker either. To put it another way, there are three types of conformance criteria: Criteria that can be expressed in a DTD. Criteria that cannot be expressed by a DTD, but can still be checked by a machine. Criteria that can only be checked by a human. A conformance checker must check for the first two. A simple DTD-based validator only checks for the first class of errors and is therefore not a conforming conformance checker according to this specification.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#conformance-checkers
ignored
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#ignored
2.2.2 Features defined in other specifications
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#features
XML-compatible
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#xml-compatible
If a form is in a browsing context whose sandboxed forms browsing context flag is set, it must not be submitted.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#sandboxSubmitBlocked
with script
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#with-script
2.1.4 Plugins
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#plugins
elements in the HTML namespace
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#elements2
scripting flag
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#scripting3
scripting is disabled
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#scripting2
4.10 Scripting
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#scripting1
2.1.3 Scripting
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#scripting0
2.1.1 XML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#xml
plugins
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#plugins0
pause
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#pause
1.5.1 How to read this specification
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#how-to
text node
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#text-node
tree order
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#tree-order
live
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#live
without script
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#without
2.2 Conformance requirements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#conformance
2.2.3 Common conformance requirements for APIs exposed to JavaScript
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#common
HTMLDocument
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#htmldocument
2. Common infrastructure
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#infrastructure
The language in this specification assumes that the user agent expands all entity references, and therefore does not include entity reference nodes in the DOM. If user agents do include entity reference nodes in the DOM, then user agents must handle them as if they were fully expanded when implementing this specification. For example, if a requirement talks about an element's child text nodes, then any text nodes that are children of an entity reference that is a child of that element would be used as well. Entity references to unknown entities must be treated as if they contained just an empty text node for the purposes of the algorithms defined in this specification.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#entity-references
embeds
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#embeds
1.5.1.1. Typographic conventions
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#typographic
HTML elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#html-elements
If the element has a charset attribute, and its value is a supported encoding, and the confidence is currently tentative, then change the encoding to the encoding given by the value of the charset attribute.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#meta-charset-during-parse
fragment case
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#fragment
2.2.1 Dependencies
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#dependencies
script browsing context
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#script3
root element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#root-element
inserted into a document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#inserted
content attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#content0
DOM attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#dom-attributes
plugin
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#plugin
The rules for handling alternative style sheets are defined in the CSS object model specification. [CSSOM]
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#alternate-style-sheets
A start tag whose tag name is "isindex"
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#isindex
form element pointer
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#form-element
8.2.3.5. The scripting state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#the-scripting
To ease migration from HTML to XHTML, UAs conforming to this specification will place elements in HTML in the http://www.w3.org/1999/xhtml namespace, at least for the purposes of the DOM and CSS. The term "elements in the HTML namespace", or "HTML elements" for short, when used in this specification, thus refers to both HTML and XHTML elements.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#html-namespace
Media Queries
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#mq
2.1.2 DOM trees
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#dom-trees
2.3 URLs
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#urls
noscript
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#noscript
Example { // this is an IDL definition };
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#example
2.1 Terminology
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1109.html#terminology
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1108&r2=1.1109&f=h
http://html5.org/tools/web-apps-tracker?from=1918&to=1919
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1108
retrieving revision 1.1109
diff -u -d -r1.1108 -r1.1109
--- Overview.html 23 Jul 2008 23:16:45 -0000 1.1108
+++ Overview.html 23 Jul 2008 23:33:44 -0000 1.1109
@@ -262,27 +262,41 @@
<ul class=toc>
<li><a href="#how-to"><span class=secno>1.5.1 </span>How to read this
specification</a>
+ <ul class=toc>
+ <li><a href="#typographic"><span class=secno>1.5.1.1.
+ </span>Typographic conventions</a>
+ </ul>
</ul>
</ul>
<li><a href="#infrastructure"><span class=secno>2. </span>Common
infrastructure</a>
<ul class=toc>
- <li><a href="#conformance"><span class=secno>2.1 </span>Conformance
+ <li><a href="#terminology"><span class=secno>2.1 </span>Terminology</a>
+ <ul class=toc>
+ <li><a href="#xml"><span class=secno>2.1.1 </span>XML</a>
+
+ <li><a href="#dom-trees"><span class=secno>2.1.2 </span>DOM trees</a>
+
+ <li><a href="#scripting0"><span class=secno>2.1.3 </span>Scripting</a>
+
+
+ <li><a href="#plugins"><span class=secno>2.1.4 </span>Plugins</a>
+ </ul>
+
+ <li><a href="#conformance"><span class=secno>2.2 </span>Conformance
requirements</a>
<ul class=toc>
- <li><a href="#dependencies"><span class=secno>2.1.1
+ <li><a href="#dependencies"><span class=secno>2.2.1
</span>Dependencies</a>
- <li><a href="#features"><span class=secno>2.1.2 </span>Features
+ <li><a href="#features"><span class=secno>2.2.2 </span>Features
defined in other specifications</a>
- <li><a href="#common"><span class=secno>2.1.3 </span>Common
+ <li><a href="#common"><span class=secno>2.2.3 </span>Common
conformance requirements for APIs exposed to JavaScript</a>
</ul>
- <li><a href="#terminology"><span class=secno>2.2 </span>Terminology</a>
-
<li><a href="#urls"><span class=secno>2.3 </span>URLs</a>
<ul class=toc>
<li><a href="#terminology0"><span class=secno>2.3.1
@@ -989,7 +1003,7 @@
</ul>
</ul>
- <li><a href="#scripting0"><span class=secno>4.10 </span>Scripting</a>
+ <li><a href="#scripting1"><span class=secno>4.10 </span>Scripting</a>
<ul class=toc>
<li><a href="#script"><span class=secno>4.10.1 </span>The
<code>script</code> element</a>
@@ -2332,9 +2346,195 @@
backwards at least once. Then it should be read by picking random sections
from the contents list and following all the cross-references.
+ <h5 id=typographic><span class=secno>1.5.1.1. </span>Typographic
+ conventions</h5>
+
+ <p>This is a definition, requirement, or explanation.
+
+ <p class=note>This is a note.
+
+ <p class=example>This is an example.
+
+ <p class=big-isue>This is an open issue.
+
+ <p class=warning>This is a warning.
+
+ <p>Element names, attribute names, code fragments, and the like are marked
+ up like <code title="">this</code>.
+
+ <p>Variables are marked up like <var title="">this</var>.
+
+ <pre class=idl>interface <dfn id=example title="">Example {
+ // this is an IDL definition
+};</dfn></pre>
+
<h2 id=infrastructure><span class=secno>2. </span>Common infrastructure</h2>
- <h3 id=conformance><span class=secno>2.1 </span>Conformance requirements</h3>
+ <h3 id=terminology><span class=secno>2.1 </span>Terminology</h3>
+
+ <p>This specification refers to both HTML and XML attributes and DOM
+ attributes, often in the same context. When it is not clear which is being
+ referred to, they are referred to as <dfn id=content0>content
+ attributes</dfn> for HTML and XML attributes, and <dfn
+ id=dom-attributes>DOM attributes</dfn> for those from the DOM. Similarly,
+ the term "properties" is used for both ECMAScript object properties and
+ CSS properties. When these are ambiguous they are qualified as object
+ properties and CSS properties respectively.
+
+ <p>The term <a href="#html-">HTML documents</a> is sometimes used in
+ contrast with <a href="#xml-documents">XML documents</a> to specifically
+ mean documents that were parsed using an <a href="#html-0">HTML parser</a>
+ (as opposed to using an XML parser or created purely through the DOM).
+
+ <p>Generally, when the specification states that a feature applies to HTML
+ or XHTML, it also includes the other. When a feature specifically only
+ applies to one of the two languages, it is called out by explicitly
+ stating that it does not apply to the other format, as in "for HTML, ...
+ (this does not apply to XHTML)".
+
+ <p>This specification uses the term <em>document</em> to refer to any use
+ of HTML, ranging from short static documents to long essays or reports
+ with rich multimedia, as well as to fully-fledged interactive
+ applications.
+
+ <p>For simplicity, terms such as <em>shown</em>, <em>displayed</em>, and
+ <em>visible</em> might sometimes be used when referring to the way a
+ document is rendered to the user. These terms are not meant to imply a
+ visual medium; they must be considered to apply to other media in
+ equivalent ways.
+
+ <p>Some of the algorithms in this specification, for historical reasons,
+ require the user agent to <dfn id=pause>pause</dfn> until some condition
+ has been met. While a user agent is paused, it must ensure that no scripts
+ execute (e.g. no event handlers, no timers, etc). User agents should
+ remain responsive to user input while paused, however, albeit without
+ letting the user interact with Web pages where that would involve invoking
+ any script.
+
+ <h4 id=xml><span class=secno>2.1.1 </span>XML</h4>
+
+ <p id=html-namespace>To ease migration from HTML to XHTML, UAs conforming
+ to this specification will place elements in HTML in the
+ <code>http://www.w3.org/1999/xhtml</code> namespace, at least for the
+ purposes of the DOM and CSS. The term "<dfn id=elements2>elements in the
+ HTML namespace</dfn>", or "<dfn id=html-elements>HTML elements</dfn>" for
+ short, when used in this specification, thus refers to both HTML and XHTML
+ elements.
+
+ <p>Unless otherwise stated, all elements defined or mentioned in this
+ specification are in the <code>http://www.w3.org/1999/xhtml</code>
+ namespace, and all attributes defined or mentioned in this specification
+ have no namespace (they are in the per-element partition).
+
+ <p>When an XML name, such as an attribute or element name, is referred to
+ in the form <code><var title="">prefix</var>:<var
+ title="">localName</var></code>, as in <code>xml:id</code> or
+ <code>svg:rect</code>, it refers to a name with the local name <var
+ title="">localName</var> and the namespace given by the prefix, as defined
+ by the following table:
+
+ <dl>
+ <dt><code title="">xml</code>
+
+ <dd><code>http://www.w3.org/XML/1998/namespace</code>
+
+ <dt><code title="">html</code>
+
+ <dd><code>http://www.w3.org/1999/xhtml</code>
+
+ <dt><code title="">svg</code>
+
+ <dd><code>http://www.w3.org/2000/svg</code>
+ </dl>
+
+ <p>Attribute names are said to be <dfn
+ id=xml-compatible>XML-compatible</dfn> if they match the <a
+ href="http://www.w3.org/TR/REC-xml/#NT-Name"><code
+ title="">Name</code></a> production defined in XML, they contain no U+003A
+ COLON (:) characters, and they do not start with three characters "<code
+ title="">xml</code>". <a href="#references">[XML]</a></p>
+ <!-- XXX case-insensitive ASCII -->
+
+ <h4 id=dom-trees><span class=secno>2.1.2 </span>DOM trees</h4>
+
+ <p>The term <dfn id=root-element>root element</dfn>, when not explicitly
+ qualified as referring to the document's root element, means the furthest
+ ancestor element node of whatever node is being discussed, or the node
+ itself if it has no ancestors. When the node is a part of the document,
+ then that is indeed the document's root element; however, if the node is
+ not currently part of the document tree, the root element will be an
+ orphaned node.
+
+ <p>An element is said to have been <dfn id=inserted title="insert an
+ element into a document">inserted into a document</dfn> when its <a
+ href="#root-element">root element</a> changes and is now the document's <a
+ href="#root-element">root element</a>.
+
+ <p>The term <dfn id=tree-order>tree order</dfn> means a pre-order,
+ depth-first traversal of DOM nodes involved (through the <code
+ title="">parentNode</code>/<code title="">childNodes</code> relationship).
+
+ <p>When it is stated that some element or attribute is <dfn id=ignored
+ title=ignore>ignored</dfn>, or treated as some other value, or handled as
+ if it was something else, this refers only to the processing of the node
+ after it is in the DOM. A user agent must not mutate the DOM in such
+ situations.
+
+ <p>The term <dfn id=text-node>text node</dfn> refers to any
+ <code>Text</code> node, including <code>CDATASection</code> nodes;
+ specifically, any <code>Node</code> with node type <code
+ title="">TEXT_NODE</code> (3) or <code title="">CDATA_SECTION_NODE</code>
+ (4). <a href="#references">[DOM3CORE]</a>
+
+ <h4 id=scripting0><span class=secno>2.1.3 </span>Scripting</h4>
+
+ <p>The construction "a <code>Foo</code> object", where <code>Foo</code> is
+ actually an interface, is sometimes used instead of the more accurate "an
+ object implementing the interface <code>Foo</code>".
+
+ <p>A DOM attribute is said to be <em>getting</em> when its value is being
+ retrieved (e.g. by author script), and is said to be <em>setting</em> when
+ a new value is assigned to it.
+
+ <p>If a DOM object is said to be <dfn id=live>live</dfn>, 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.
+
+ <p>The terms <em>fire</em> and <em>dispatch</em> are used interchangeably
+ in the context of events, as in the DOM Events specifications. <a
+ href="#references">[DOM3EVENTS]</a>
+
+ <h4 id=plugins><span class=secno>2.1.4 </span>Plugins</h4>
+
+ <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content
+ handler, typically a third-party content handler, for Web content types
+ that are not supported by the user agent natively, or for content types
+ that do not expose a DOM, that supports rendering the content as part of
+ the user agent's interface.
+
+ <p class=example>One example of a plugin would be a PDF viewer that is
+ instantiated in a <a href="#browsing1">browsing context</a> 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.
+
+ <p class=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. <a href="#references">[NPAPI]</a>
+
+ <p class=warning>Browsers should take extreme care when interacting with
+ external content intended for <a href="#plugin" title=plugin>plugins</a>.
+ 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.
+
+ <h3 id=conformance><span class=secno>2.2 </span>Conformance requirements</h3>
<p>All diagrams, examples, and notes in this specification are
non-normative, as are all sections explicitly marked non-normative.
@@ -2440,7 +2640,7 @@
<p>Conformance checkers must check that the input document conforms when
parsed without a <a href="#browsing1">browsing context</a> (meaning that
no scripts are run, and that the parser's <a
- href="#scripting2">scripting flag</a> is disabled), and should also
+ href="#scripting3">scripting flag</a> is disabled), and should also
check that the input document conforms when parsed with a <a
href="#browsing1">browsing context</a> in which scripts execute, and
that the scripts never cause non-conforming states to occur other than
@@ -2609,7 +2809,7 @@
be treated as if they contained just an empty text node for the purposes
of the algorithms defined in this specification.
- <h4 id=dependencies><span class=secno>2.1.1 </span>Dependencies</h4>
+ <h4 id=dependencies><span class=secno>2.2.1 </span>Dependencies</h4>
<p>This specification relies on several other underlying specifications.
@@ -2665,7 +2865,7 @@
on character encodings, image formats, audio formats, and video formats in
the respective sections.
- <h4 id=features><span class=secno>2.1.2 </span>Features defined in other
+ <h4 id=features><span class=secno>2.2.2 </span>Features defined in other
specifications</h4>
<p class=big-issue>this section will be removed at some point
@@ -2700,7 +2900,7 @@
<p class=big-issue>See <a
href="http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8</a>
- <h4 id=common><span class=secno>2.1.3 </span>Common conformance
+ <h4 id=common><span class=secno>2.2.3 </span>Common conformance
requirements for APIs exposed to JavaScript</h4>
<p class=big-issue>This section will eventually be removed in favour of
@@ -2735,162 +2935,6 @@
requirement in the canvas section for toDataURL() and
getContext(). -->
- <h3 id=terminology><span class=secno>2.2 </span>Terminology</h3>
-
- <p>This specification refers to both HTML and XML attributes and DOM
- attributes, often in the same context. When it is not clear which is being
- referred to, they are referred to as <dfn id=content0>content
- attributes</dfn> for HTML and XML attributes, and <dfn
- id=dom-attributes>DOM attributes</dfn> for those from the DOM. Similarly,
- the term "properties" is used for both ECMAScript object properties and
- CSS properties. When these are ambiguous they are qualified as object
- properties and CSS properties respectively.
-
- <p id=html-namespace>To ease migration from HTML to XHTML, UAs conforming
- to this specification will place elements in HTML in the
- <code>http://www.w3.org/1999/xhtml</code> namespace, at least for the
- purposes of the DOM and CSS. The term "<dfn id=elements2>elements in the
- HTML namespace</dfn>", or "<dfn id=html-elements>HTML elements</dfn>" for
- short, when used in this specification, thus refers to both HTML and XHTML
- elements.
-
- <p>Unless otherwise stated, all elements defined or mentioned in this
- specification are in the <code>http://www.w3.org/1999/xhtml</code>
- namespace, and all attributes defined or mentioned in this specification
- have no namespace (they are in the per-element partition).
-
- <p>When an XML name, such as an attribute or element name, is referred to
- in the form <code><var title="">prefix</var>:<var
- title="">localName</var></code>, as in <code>xml:id</code> or
- <code>svg:rect</code>, it refers to a name with the local name <var
- title="">localName</var> and the namespace given by the prefix, as defined
- by the following table:
-
- <dl>
- <dt><code title="">xml</code>
-
- <dd><code>http://www.w3.org/XML/1998/namespace</code>
-
- <dt><code title="">html</code>
-
- <dd><code>http://www.w3.org/1999/xhtml</code>
-
- <dt><code title="">svg</code>
-
- <dd><code>http://www.w3.org/2000/svg</code>
- </dl>
-
- <p>Attribute names are said to be <dfn
- id=xml-compatible>XML-compatible</dfn> if they match the <a
- href="http://www.w3.org/TR/REC-xml/#NT-Name"><code
- title="">Name</code></a> production defined in XML, they contain no U+003A
- COLON (:) characters, and they do not start with three characters "<code
- title="">xml</code>". <a href="#references">[XML]</a></p>
- <!-- XXX case-insensitive ASCII -->
-
- <p>The term <a href="#html-">HTML documents</a> is sometimes used in
- contrast with <a href="#xml-documents">XML documents</a> to specifically
- mean documents that were parsed using an <a href="#html-0">HTML parser</a>
- (as opposed to using an XML parser or created purely through the DOM).
-
- <p>Generally, when the specification states that a feature applies to HTML
- or XHTML, it also includes the other. When a feature specifically only
- applies to one of the two languages, it is called out by explicitly
- stating that it does not apply to the other format, as in "for HTML, ...
- (this does not apply to XHTML)".
-
- <p>This specification uses the term <em>document</em> to refer to any use
- of HTML, ranging from short static documents to long essays or reports
- with rich multimedia, as well as to fully-fledged interactive
- applications.
-
- <p>The term <dfn id=root-element>root element</dfn>, when not explicitly
- qualified as referring to the document's root element, means the furthest
- ancestor element node of whatever node is being discussed, or the node
- itself if it has no ancestors. When the node is a part of the document,
- then that is indeed the document's root element; however, if the node is
- not currently part of the document tree, the root element will be an
- orphaned node.
-
- <p>An element is said to have been <dfn id=inserted title="insert an
- element into a document">inserted into a document</dfn> when its <a
- href="#root-element">root element</a> changes and is now the document's <a
- href="#root-element">root element</a>.
-
- <p>The term <dfn id=tree-order>tree order</dfn> means a pre-order,
- depth-first traversal of DOM nodes involved (through the <code
- title="">parentNode</code>/<code title="">childNodes</code> relationship).
-
- <p>When it is stated that some element or attribute is <dfn id=ignored
- title=ignore>ignored</dfn>, or treated as some other value, or handled as
- if it was something else, this refers only to the processing of the node
- after it is in the DOM. A user agent must not mutate the DOM in such
- situations.
-
- <p>For simplicity, terms such as <em>shown</em>, <em>displayed</em>, and
- <em>visible</em> might sometimes be used when referring to the way a
- document is rendered to the user. These terms are not meant to imply a
- visual medium; they must be considered to apply to other media in
- equivalent ways.
-
- <p>The construction "a <code>Foo</code> object", where <code>Foo</code> is
- actually an interface, is sometimes used instead of the more accurate "an
- object implementing the interface <code>Foo</code>".
-
- <p>A DOM attribute is said to be <em>getting</em> when its value is being
- retrieved (e.g. by author script), and is said to be <em>setting</em> when
- a new value is assigned to it.
-
- <p>If a DOM object is said to be <dfn id=live>live</dfn>, 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.
-
- <p>The terms <em>fire</em> and <em>dispatch</em> are used interchangeably
- in the context of events, as in the DOM Events specifications. <a
- href="#references">[DOM3EVENTS]</a>
-
- <p>The term <dfn id=text-node>text node</dfn> refers to any
- <code>Text</code> node, including <code>CDATASection</code> nodes;
- specifically, any <code>Node</code> with node type <code
- title="">TEXT_NODE</code> (3) or <code title="">CDATA_SECTION_NODE</code>
- (4). <a href="#references">[DOM3CORE]</a>
-
- <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content
- handler, typically a third-party content handler, for Web content types
- that are not supported by the user agent natively, or for content types
- that do not expose a DOM, that supports rendering the content as part of
- the user agent's interface.
-
- <p class=example>One example of a plugin would be a PDF viewer that is
- instantiated in a <a href="#browsing1">browsing context</a> 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.
-
- <p class=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. <a href="#references">[NPAPI]</a>
-
- <p class=warning>Browsers should take extreme care when interacting with
- external content intended for <a href="#plugin" title=plugin>plugins</a>.
- 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.
-
- <p>Some of the algorithms in this specification, for historical reasons,
- require the user agent to <dfn id=pause>pause</dfn> until some condition
- has been met. While a user agent is paused, it must ensure that no scripts
- execute (e.g. no event handlers, no timers, etc). User agents should
- remain responsive to user input while paused, however, albeit without
- letting the user interact with Web pages where that would involve invoking
- any script.
-
<h3 id=urls><span class=secno>2.3 </span>URLs</h3>
<p>This specification defines the term <a href="#url">URL</a>, and defines
@@ -6781,7 +6825,7 @@
attribute <a href="#htmlelement">HTMLElement</a> <a href="#body" title=dom-document-body>body</a>;
readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#images0" title=dom-document-images>images</a>;
readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#embeds" title=dom-document-embeds>embeds</a>;
- readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#plugins" title=dom-document-plugins>plugins</a>;
+ readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#plugins0" title=dom-document-plugins>plugins</a>;
readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#links0" title=dom-document-links>links</a>;
readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#forms0" title=dom-document-forms>forms</a>;
readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#anchors" title=dom-document-anchors>anchors</a>;
@@ -7136,7 +7180,7 @@
<code>Document</code> node, whose filter matches only <code><a
href="#embed">embed</a></code> elements.
- <p>The <dfn id=plugins
+ <p>The <dfn id=plugins0
title=dom-document-plugins><code>plugins</code></dfn> attribute must
return the same object as that returned by the <code
title=dom-document-embeds><a href="#embeds">embeds</a></code> attribute.
@@ -25159,7 +25203,7 @@
context whose <a href="#sandboxed3">sandboxed forms browsing context
flag</a> is set, it must not be submitted.
- <h3 id=scripting0><span class=secno>4.10 </span>Scripting</h3>
+ <h3 id=scripting1><span class=secno>4.10 </span>Scripting</h3>
<p>Scripts allow authors to add interactivity to their documents.
@@ -25847,7 +25891,7 @@
<p class=note>All these contortions are required because, for historical
reasons, the <code><a href="#noscript">noscript</a></code> element is
handled differently by the <a href="#html-0">HTML parser</a> based on
- whether <a href="#scripting2" title="scripting flag">scripting was enabled
+ whether <a href="#scripting3" title="scripting flag">scripting was enabled
or not</a> when the parser was invoked. The element is not allowed in XML,
because in XML the parser is not affected by such state, and thus the
element would not have the desired effect.
@@ -31544,7 +31588,7 @@
associated explicitly with a <a href="#browsing1">browsing context</a>
when it is created.
- <p>It is said that <dfn id=scripting1>scripting is disabled</dfn> in a <a
+ <p>It is said that <dfn id=scripting2>scripting is disabled</dfn> in a <a
href="#script2">script execution context</a> when any of the following
conditions are true:
@@ -31572,7 +31616,7 @@
<p>A node is said to be <dfn id=without>without script</dfn> if either the
<code>Document</code> object of the node (the node itself, if it is itself
a <code>Document</code> object) does not have an associated <a
- href="#browsing1">browsing context</a>, or <a href="#scripting1">scripting
+ href="#browsing1">browsing context</a>, or <a href="#scripting2">scripting
is disabled</a> in that <a href="#browsing1">browsing context</a>.
<p>A node is said to be <dfn id=with-script>with script</dfn> if it is not
@@ -31583,7 +31627,7 @@
are less confusing are also way, way longer.
<p>When a script is to be executed in a <a href="#script2">script execution
- context</a> in which <a href="#scripting1">scripting is disabled</a>, the
+ context</a> in which <a href="#scripting2">scripting is disabled</a>, the
script must do nothing and return nothing (a void return value).
<p class=note>Thus, for instance, enabling <code
@@ -45528,7 +45572,7 @@
<h5 id=the-scripting><span class=secno>8.2.3.5. </span>The scripting state</h5>
- <p>The <dfn id=scripting2>scripting flag</dfn> is set to "enabled" if the
+ <p>The <dfn id=scripting3>scripting flag</dfn> is set to "enabled" if the
<code>Document</code> with which the parser is associated was <a
href="#with-script">with script</a> when the parser was created, and
"disabled" otherwise.
@@ -48256,7 +48300,7 @@
algorithm</a>.</p>
<dt>A start tag whose tag name is "noscript", if the <a
- href="#scripting2">scripting flag</a> is enabled
+ href="#scripting3">scripting flag</a> is enabled
<dt>A start tag whose tag name is one of: "noframes", "style"
@@ -48265,7 +48309,7 @@
algorithm</a>.</p>
<dt>A start tag whose tag name is "noscript", if the <a
- href="#scripting2">scripting flag</a> is disabled
+ href="#scripting3">scripting flag</a> is disabled
<dd>
<p><a href="#insert0">Insert an HTML element</a> for the token.</p>
@@ -49524,7 +49568,7 @@
<dt>A start tag whose tag name is one of: "iframe", "noembed"
<dt>A start tag whose tag name is "noscript", if the <a
- href="#scripting2">scripting flag</a> is enabled
+ href="#scripting3">scripting flag</a> is enabled
<dd>
<p>Follow the <a href="#generic">generic CDATA element parsing
@@ -51450,7 +51494,7 @@
<dt>If it is a <code><a href="#noscript">noscript</a></code> element
- <dd>If the <a href="#scripting2">scripting flag</a> is enabled, set the
+ <dd>If the <a href="#scripting3">scripting flag</a> is enabled, set the
<a href="#content3">content model flag</a> to the CDATA state.
Otherwise, set the <a href="#content3">content model flag</a> to the
PCDATA state.
Received on Thursday, 24 July 2008 07:16:27 UTC