[html5] r1451 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu Apr 17 14:15:47 PDT 2008
Author: ianh
Date: 2008-04-17 14:15:45 -0700 (Thu, 17 Apr 2008)
New Revision: 1451
Modified:
index
source
Log:
[] (0) Define document.embeds, document.applets; s/behaviour/behavior/
Modified: index
===================================================================
--- index 2008-04-17 20:13:10 UTC (rev 1450)
+++ index 2008-04-17 21:15:45 UTC (rev 1451)
@@ -1748,7 +1748,8 @@
</ul>
</ul>
- <li><a href="#rendering"><span class=secno>10. </span>Rendering</a>
+ <li><a href="#rendering"><span class=secno>10. </span>Rendering and
+ user-agent behavior</a>
<ul class=toc>
<li><a href="#rendering0"><span class=secno>10.1 </span>Rendering and
the DOM</a>
@@ -1759,6 +1760,13 @@
<li><a href="#the-icon"><span class=secno>10.2.1 </span>The 'icon'
property</a>
</ul>
+
+ <li><a href="#obsolete"><span class=secno>10.3 </span>Obsolete
+ elements</a>
+ <ul class=toc>
+ <li><a href="#the-applet"><span class=secno>10.3.1 </span>The
+ <code>applet</code> element</a>
+ </ul>
</ul>
<li><a href="#no"><span class=secno>11. </span>Things that you can't do
@@ -2157,7 +2165,7 @@
<p>Some conformance requirements are phrased as requirements on elements,
attributes, methods or objects. Such requirements fall into two
categories; those describing content model restrictions, and those
- describing implementation behaviour. The former category of requirements
+ describing implementation behavior. The former category of requirements
are requirements on documents and authoring tools. The second category are
requirements on user agents.
@@ -2550,7 +2558,7 @@
id=html->HTML documents</dfn> when they are created. Whether a document is
an <a href="#html-" title="HTML documents">HTML document</a> or an <a
href="#xml-documents" title="XML documents">XML document</a> affects the
- behaviour of certain APIs, as well as a few CSS rendering rules. <a
+ behavior of certain APIs, as well as a few CSS rendering rules. <a
href="#refsCSS21">[CSS21]</a>
<p class=note>A <code>Document</code> object created by the <code
@@ -2593,8 +2601,8 @@
attribute DOMString <a href="#dir1" title=dom-document-dir>dir</a>;
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 <span>HTMLCollection</span> <span title="dom-document-applets">applets</span>;
---> 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="#embeds" title=dom-document-embeds>embeds</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>;
NodeList <a href="#getelementsbyname" title=dom-document-getElementsByName>getElementsByName</a>(in DOMString elementName);
@@ -3090,11 +3098,12 @@
collection that matches the following requirements:
<ul>
- <li>It is an <code><a href="#a">a</a></code>, <code>applet</code>,
- <code><a href="#area">area</a></code>, <code>form</code>, <code><a
- href="#img">img</a></code>, or <code><a href="#object">object</a></code>
- element with a <code title=attr-name>name</code> attribute equal to <var
- title="">key</var>, or,
+ <li>It is an <code><a href="#a">a</a></code>, <code><a
+ href="#applet">applet</a></code>, <code><a href="#area">area</a></code>,
+ <code>form</code>, <code><a href="#img">img</a></code>, or <code><a
+ href="#object">object</a></code> element with a <code
+ title=attr-name>name</code> attribute equal to <var title="">key</var>,
+ or,
<li>It is an <a href="#html-elements" title="HTML elements">HTML
element</a> of any kind with an <code title=attr-id><a
@@ -3184,7 +3193,7 @@
must return the number of nodes <span>represented by the
collection</span>.
- <p>On setting, the behaviour depends on whether the new value is equal to,
+ <p>On setting, the behavior depends on whether the new value is equal to,
greater than, or less than the number of nodes <span>represented by the
collection</span> at that time. If the number is the same, then setting
the attribute must do nothing. If the new value is greater, then <var
@@ -3573,6 +3582,12 @@
<code>Document</code> node, whose filter matches only <code><a
href="#img">img</a></code> elements.
+ <p>The <dfn id=embeds title=dom-document-embeds><code>embeds</code></dfn>
+ attribute must return an <code><a
+ href="#htmlcollection0">HTMLCollection</a></code> rooted at the
+ <code>Document</code> node, whose filter matches only <code><a
+ href="#embed">embed</a></code> elements.
+
<p>The <dfn id=links0 title=dom-document-links><code>links</code></dfn>
attribute must return an <code><a
href="#htmlcollection0">HTMLCollection</a></code> rooted at the
@@ -3601,16 +3616,16 @@
title=dom-document-getElementsByName><code>getElementsByName(<var
title="">name</var>)</code></dfn> method a string <var
title="">name</var>, and must return a live <code>NodeList</code>
- containing all the <code><a href="#a">a</a></code>, <code>applet</code>,
- <code>button</code>, <code>form</code>, <!-- frame? frameset?
- XXX--><code><a
- href="#iframe">iframe</a></code>, <code><a href="#img">img</a></code>,
- <code>input</code>, <code><a href="#map">map</a></code>, <code><a
- href="#meta0">meta</a></code>, <code><a
- href="#object">object</a></code>,<!-- param?
- XXX--> <code>select</code>,
- and <code>textarea</code> elements in that document that have a <code
- title="">name</code> attribute whose value is
+ containing all the <code><a href="#a">a</a></code>, <code><a
+ href="#applet">applet</a></code>, <code>button</code>, <code>form</code>,
+ <!-- frame? frameset?
+ XXX--><code><a href="#iframe">iframe</a></code>,
+ <code><a href="#img">img</a></code>, <code>input</code>, <code><a
+ href="#map">map</a></code>, <code><a href="#meta0">meta</a></code>,
+ <code><a href="#object">object</a></code>,<!-- param?
+ XXX-->
+ <code>select</code>, and <code>textarea</code> elements in that document
+ that have a <code title="">name</code> attribute whose value is
equal<!-- XXX case sensitivity --> to the <var title="">name</var>
argument.</p>
<!-- XXX what about XHTML? -->
@@ -3695,7 +3710,7 @@
<p class=issue>bz argues that innerHTML should be called something else on
XML documents and XML elements. Is the sanity worth the migration pain?
- <p>Because these APIs interact with the parser, their behaviour varies
+ <p>Because these APIs interact with the parser, their behavior varies
depending on whether they are used with <a href="#html-">HTML
documents</a> (and the <a href="#html-0">HTML parser</a>) or XHTML in <a
href="#xml-documents">XML documents</a> (and the <span>XML parser</span>).
@@ -6049,7 +6064,7 @@
<h5 id=metadata><span class=secno>3.3.3.1. </span>Metadata content</h5>
<p><dfn id=metadata0>Metadata content</dfn> is content that sets up the
- presentation or behaviour of the rest of the content, or that sets up the
+ presentation or behavior of the rest of the content, or that sets up the
relationship of the document with other documents, or that conveys other
"out of band" information.
@@ -6769,7 +6784,7 @@
attributes are ignored and any associated CSS dropped, the page is still
usable.
- <p>User agents must not derive any implementation behaviour from these
+ <p>User agents must not derive any implementation behavior from these
attributes or values. Specifications intended for user agents must not
define these attributes to have any meaningful values.
@@ -7319,7 +7334,7 @@
might be hyperlinks). User agents should process the links on a per-link
basis, not a per-element basis.
- <p>The exact behaviour for links to external resources depends on the exact
+ <p>The exact behavior for links to external resources depends on the exact
relationship, as defined for the relevant link type. Some of the
attributes control whether or not the external resource is to be applied
(as defined below). For external resources that are represented in the DOM
@@ -14314,7 +14329,7 @@
data itself.</p>
<!-- XXX
make it an interactive element
- default activation behaviour is to do the play() if paused, pause()
+ default activation behavior is to do the play() if paused, pause()
otherwise
-->
@@ -17791,7 +17806,7 @@
> and the implementations need to make sure they handle any edge cases
> that the underlying graphics library does differently. (SVG Tiny 1.2
> appears to skip some of the problems by leaving things undefined and
-> allowing whatever behaviour the graphics library has.)
+> allowing whatever behavior the graphics library has.)
-->
<h6 id=shadows><span class=secno>3.12.11.1.6. </span><dfn
@@ -18053,7 +18068,7 @@
title="">x1</var>, <var title="">y1</var>, <var title="">x2</var>, <var
title="">y2</var>, <var title="">radius</var>)</code></dfn> method must do
nothing if the context has no subpaths. If the context <em>does</em> have
- a subpath, then the behaviour depends on the arguments and the last point
+ a subpath, then the behavior depends on the arguments and the last point
in the subpath.
<p>Negative values for <var title="">radius</var> must cause the
@@ -19706,7 +19721,7 @@
parent is a <code><a href="#tfoot0">tfoot</a></code> element, still in
tree order.
- <p>The behaviour of the <dfn id=insertrow
+ <p>The behavior of the <dfn id=insertrow
title=dom-table-insertRow><code>insertRow(<var
title="">index</var>)</code></dfn> method depends on the state of the
table. When it is called, the method must act as required by the first
@@ -22758,7 +22773,7 @@
title=dom-datagrid-data><a href="#data2">data</a></code> attribute is
null. It must act as described in this section.
- <p>The behaviour of the default data provider depends on the nature of the
+ <p>The behavior of the default data provider depends on the nature of the
first element child of the <code><a href="#datagrid0">datagrid</a></code>.
<dl class=switch>
@@ -23831,10 +23846,10 @@
href="#getrowmenu">getRowMenu</a></code> method.
<p>The exact algorithm used to populate the data grid is not defined here,
- since it will differ based on the presentation used. However, the
- behaviour of user agents must be consistent with the descriptions above.
- For example, it would be non-conformant for a user agent to make cells
- have both a checkbox and be editable, as the descriptions above state that
+ since it will differ based on the presentation used. However, the behavior
+ of user agents must be consistent with the descriptions above. For
+ example, it would be non-conformant for a user agent to make cells have
+ both a checkbox and be editable, as the descriptions above state that
cells that have a checkbox cannot be edited.</p>
<!-- XXX speaking of which, do we actually want that
limitation? -->
@@ -23940,7 +23955,7 @@
<p>If a cell is a cell whose value <a href="#cellType1">can be cycled
between multiple states</a>, then the user must be able to activate the
- cell to cycle its value. When the user activates this "cycling" behaviour
+ cell to cycle its value. When the user activates this "cycling" behavior
of a cell, then the <code><a href="#datagrid0">datagrid</a></code> must
invoke the data provider's <code title=dom-provider-cycleCell><a
href="#cyclecell">cycleCell()</a></code> method, with a <code><a
@@ -24319,7 +24334,7 @@
content attributes.
<p>The <dfn id=click0 title=dom-command-click><code>click()</code></dfn>
- method's behaviour depends on the value of the <code
+ method's behavior depends on the value of the <code
title=attr-command-type><a href="#type13">type</a></code> attribute of the
element, as follows:
@@ -24604,7 +24619,7 @@
<p>The list corresponding to a particular <code><a
href="#menu">menu</a></code> element is built by iterating over its child
nodes. For each child node in <a href="#tree-order">tree order</a>, the
- required behaviour depends on what the node is, as follows:
+ required behavior depends on what the node is, as follows:
<dl class=switch>
<dt>An element that <a href="#command1" title=concept-command>defines a
@@ -25241,9 +25256,9 @@
attribute, and false otherwise.
<p>The <a href="#action" title=command-facet-Action>Action</a> of the
- command is to invoke the behaviour described in the definition of the
- <code title=dom-command-click><a href="#click0">click()</a></code> method
- of the <code><a href="#htmlcommandelement">HTMLCommandElement</a></code>
+ command is to invoke the behavior described in the definition of the <code
+ title=dom-command-click><a href="#click0">click()</a></code> method of the
+ <code><a href="#htmlcommandelement">HTMLCommandElement</a></code>
interface.</p>
<!-- XXX update to
point to dom-click when we remove dom-command-click -->
@@ -29864,7 +29879,7 @@
<code>Document</code> object, as an absolute IRI reference.
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
- should we do?: the behaviour depends on the context in which the
+ should we do?: the behavior depends on the context in which the
script that set the attribute is running. If the script ran as the
direct result of the execution of a <code>script</code> element in
the document represented by the <code>Location</code> object's
@@ -32625,7 +32640,7 @@
parallel with the primary request, and is independent of the result of
that request.
- <p>User agents should allow the user to adjust this behaviour, for example
+ <p>User agents should allow the user to adjust this behavior, for example
in conjunction with a setting that disables the sending of HTTP <code
title="">Referer</code> headers. Based on the user's preferences, UAs may
either <a href="#ignored">ignore</a> the <code
@@ -34163,9 +34178,9 @@
href="#phrasing0">phrasing content</a> is not allowed (e.g. inside an
empty <code><a href="#ol">ol</a></code> element), then the user agent
must not insert the text directly at the caret position. In such cases
- the behaviour is UA-dependent, but user agents must not, in response to
- a request to insert text, generate a DOM that is less conformant than
- the DOM prior to the request.</p>
+ the behavior is UA-dependent, but user agents must not, in response to a
+ request to insert text, generate a DOM that is less conformant than the
+ DOM prior to the request.</p>
<p>User agents should allow users to insert new paragraphs into elements
that contains only content other than paragraphs.</p>
@@ -34194,7 +34209,7 @@
title=event-keydown>keydown</code> event whose identifier is the "Enter"
key and that has no modifiers set.</p>
- <p>The exact behaviour is UA-dependent, but user agents must not, in
+ <p>The exact behavior is UA-dependent, but user agents must not, in
response to a request to break a paragraph, generate a DOM that is less
conformant than the DOM prior to the request.
@@ -34213,7 +34228,7 @@
href="#phrasing0">phrasing content</a> is not allowed (e.g. in an empty
<code><a href="#ol">ol</a></code> element), then the user agent must not
insert the <code><a href="#br">br</a></code> element directly at the
- caret position. In such cases the behaviour is UA-dependent, but user
+ caret position. In such cases the behavior is UA-dependent, but user
agents must not, in response to a request to insert a line separator,
generate a DOM that is less conformant than the DOM prior to the
request.
@@ -34234,7 +34249,7 @@
href="#a-selection" title="the selection">selection</a> whose start and
end points do not share a common parent node.</p>
- <p>In any case, the exact behaviour is UA-dependent, but user agents must
+ <p>In any case, the exact behavior is UA-dependent, but user agents must
not, in response to a request to delete text or an element, generate a
DOM that is less conformant than the DOM prior to the request.
@@ -34263,7 +34278,7 @@
element should only be used if the user agent is sure that the user
means to indicate importance.</p>
- <p>The exact behaviour is UA-dependent, but user agents must not, in
+ <p>The exact behavior is UA-dependent, but user agents must not, in
response to a request to wrap semantics around some text or to insert or
remove a semantic element, generate a DOM that is less conformant than
the DOM prior to the request.
@@ -34567,7 +34582,7 @@
the processing model described below causes one of these events to be
fired, the event fired must use the <code><a
href="#dragevent">DragEvent</a></code> interface defined above, must have
- the bubbling and cancelable behaviours given in the table below, and must
+ the bubbling and cancelable behaviors given in the table below, and must
have the context information set up as described after the table, with the
<code title=dom-UIEvent-view>view</code> attribute set to the view with
which the user interacted to trigger the drag-and-drop event, and the
@@ -35551,7 +35566,7 @@
<p>The <dfn id=adddata title=dom-UndoManager-add><code>add(<var
title="">data</var>, <var title="">title</var>)</code></dfn> method's
- behaviour depends on the current state. Normally, it must insert the <var
+ behavior depends on the current state. Normally, it must insert the <var
title="">data</var> object passed as an argument into the <a
href="#undo-transaction">undo transaction history</a> immediately before
the <a href="#current3">undo position</a>, optionally remembering the
@@ -36364,7 +36379,7 @@
requested that the selection <a href="#contenteditable-wrapSemantic">be
wrapped in the semantics</a> of the <code><a href="#ol">ol</a></code>
element (or unwrapped, or, if there is no selection, have that semantic
- inserted or removed — the exact behaviour is UA-defined).
+ inserted or removed — the exact behavior is UA-defined).
<dd><strong>Enabled When:</strong> The document is <a href="#ready">ready
for editing host commands</a>.
@@ -36383,7 +36398,7 @@
requested that the selection <a href="#contenteditable-wrapSemantic">be
wrapped in the semantics</a> of the <code><a href="#ul">ul</a></code>
element (or unwrapped, or, if there is no selection, have that semantic
- inserted or removed — the exact behaviour is UA-defined).
+ inserted or removed — the exact behavior is UA-defined).
<dd><strong>Enabled When:</strong> The document is <a href="#ready">ready
for editing host commands</a>.
@@ -36516,7 +36531,7 @@
requested that the selection <a href="#contenteditable-wrapSemantic">be
wrapped in the semantics</a> of the <code><a href="#sup">sup</a></code>
element (or unwrapped, or, if there is no selection, have that semantic
- inserted or removed — the exact behaviour is UA-defined).
+ inserted or removed — the exact behavior is UA-defined).
<dd><strong>Enabled When:</strong> The document is <a href="#ready">ready
for editing host commands</a>.
@@ -37271,7 +37286,7 @@
<p>The <dfn id=send title=dom-Connection-send><code>send()</code></dfn>
method transmits data using the connection. If the connection is not yet
established, it must raise an <code>INVALID_STATE_ERR</code> exception. If
- the connection <em>is</em> established, then the behaviour depends on the
+ the connection <em>is</em> established, then the behavior depends on the
connection type, as described below.
<p>The <dfn id=disconnect
@@ -39856,8 +39871,8 @@
<dd>
<p>The following HTML elements introduce new <a href="#have-an"
title="has an element in scope">scopes</a> for various parts of the
- parsing: <code>applet</code>, <code>button</code>, <code><a
- href="#caption0">caption</a></code>, <code><a
+ parsing: <code><a href="#applet">applet</a></code>, <code>button</code>,
+ <code><a href="#caption0">caption</a></code>, <code><a
href="#html">html</a></code>, <code>marquee</code>, <code><a
href="#object">object</a></code>, <code><a
href="#table">table</a></code>, <code><a href="#td">td</a></code> and
@@ -39916,7 +39931,7 @@
state:</p>
<ul class=brief>
- <li><code>applet</code>
+ <li><code><a href="#applet">applet</a></code>
<li><code><a href="#caption0">caption</a></code>
@@ -39965,10 +39980,10 @@
<p>The list contains elements in the <a href="#formatting">formatting</a>
category, and scope markers. The scope markers are inserted when entering
- <code>applet</code> elements, buttons, <code><a
+ <code><a href="#applet">applet</a></code> elements, buttons, <code><a
href="#object">object</a></code> elements, marquees, table cells, and
table captions, and are used to prevent formatting from "leaking" into
- <code>applet</code> elements, buttons, <code><a
+ <code><a href="#applet">applet</a></code> elements, buttons, <code><a
href="#object">object</a></code> elements, marquees, and tables.
<p>When the steps below require the UA to <dfn id=reconstruct>reconstruct
@@ -40071,17 +40086,17 @@
which may have various side-effects, and either switches the state machine
to a new state to <em>reconsume</em> the same character, or switches it to
a new state (to consume the next character), or repeats the same state (to
- consume the next character). Some states have more complicated behaviour
+ consume the next character). Some states have more complicated behavior
and can consume several characters before switching to another state.
- <p>The exact behaviour of certain states depends on a <dfn
+ <p>The exact behavior of certain states depends on a <dfn
id=content2>content model flag</dfn> that is set after certain tokens are
emitted. The flag has several states: <em title="">PCDATA</em>, <em
title="">RCDATA</em>, <em title="">CDATA</em>, and <em
title="">PLAINTEXT</em>. Initially it must be in the PCDATA state. In the
RCDATA and CDATA states, a further <dfn id=escape>escape flag</dfn> is
- used to control the behaviour of the tokeniser. It is either true or
- false, and initially must be set to the false state. The <span>insertion
+ used to control the behavior of the tokeniser. It is either true or false,
+ and initially must be set to the false state. The <span>insertion
mode</span> and the <a href="#stack">stack of open elements</a> also
affects tokenisation.
@@ -40219,7 +40234,7 @@
<dt><dfn id=tag-open>Tag open state</dfn>
<dd>
- <p>The behaviour of this state depends on the <a href="#content2">content
+ <p>The behavior of this state depends on the <a href="#content2">content
model flag</a>.</p>
<dl>
@@ -41518,7 +41533,7 @@
title="entity data state">in text</a> and <a href="#entity0" title="entity
in attribute value state">in attributes</a>.
- <p>The behaviour depends on the identity of the next character (the one
+ <p>The behavior depends on the identity of the next character (the one
immediately after the U+0026 AMPERSAND character):
<dl class=switch>
@@ -41550,7 +41565,7 @@
<dd>
<p>Consume the U+0023 NUMBER SIGN.</p>
- <p>The behaviour further depends on the character after the U+0023 NUMBER
+ <p>The behavior further depends on the character after the U+0023 NUMBER
SIGN:</p>
<dl class=switch>
@@ -48165,7 +48180,8 @@
value representing the serialised form of the
<code>CSSStyleDeclaration</code> object. <a href="#refsCSSOM">[CSSOM]</a>
- <h2 id=rendering><span class=secno>10. </span>Rendering</h2>
+ <h2 id=rendering><span class=secno>10. </span>Rendering and user-agent
+ behavior</h2>
<!-- XXX
Rendering
@@ -48213,7 +48229,7 @@
border edge.</p>
<!-- XXX horiz pos given bidi, and not
scrolling when not required to? -->
- <!-- Elements that have been dropped: ACRONYM APPLET B BASEFONT BLINK
+ <!-- Elements that have been dropped: ACRONYM B BASEFONT BLINK
BIG CENTER DIR DIV FONT FRAME FRAMESET I ISINDEX MARQUEE NOEMBED
NOFRAMES S SPACER STRIKE TT U -->
<!-- XXX bits and pieces that were removed from the semantic parts:
@@ -48300,6 +48316,29 @@
title=command-attribute>command</code> attribute, but when the property
computes to an actual image, it should use that image instead.
+ <h3 id=obsolete><span class=secno>10.3 </span>Obsolete elements</h3>
+
+ <h4 id=the-applet><span class=secno>10.3.1 </span>The <dfn
+ id=applet><code>applet</code></dfn> element</h4>
+
+ <p>The <code><a href="#applet">applet</a></code> element is a Java-specific
+ variant of the <code><a href="#embed">embed</a></code> element. In HTML5
+ the <code><a href="#applet">applet</a></code> element is obsoleted so that
+ all extension frameworks (Java, .NET, Flash, etc) are handled in a
+ consistent manner.
+
+ <p class=big-issue>define how the element works, if supported
+
+ <pre class=idl>[XXX=HTMLDocument] interface {
+ readonly attribute <a href="#htmlcollection0">HTMLCollection</a> <a href="#applets" title=dom-document-applets>applets</a>;
+};</pre>
+
+ <p>The <dfn id=applets
+ title=dom-document-applets><code>applets</code></dfn> attribute must
+ return an <code><a href="#htmlcollection0">HTMLCollection</a></code>
+ rooted at the <code>Document</code> node, whose filter matches only
+ <code><a href="#applet">applet</a></code> elements.
+
<h2 id=no><span class=secno>11. </span>Things that you can't do with this
specification because they are better handled using other technologies
that are further described herein</h2>
@@ -48559,7 +48598,7 @@
> I have use cases for both...I have a more desperate business need for
> the latter (and have build apps using the gross APIs out there today)
> but there are a lot of circumstances where an editor that already has
-> all standard HTML editing behaviour would be fine.
+> all standard HTML editing behavior would be fine.
>
- Paul Prescod
@@ -49672,9 +49711,9 @@
analogous way. If the element is on the right of the page, the menu
should drop to the left, and vice versa.</p>
- <p>UAs should implement the drop-down behaviour in more
+ <p>UAs should implement the drop-down behavior in more
platform-appropriate ways if the platform conventions differ from
- the behaviour described above.</p>
+ the behavior described above.</p>
Modified: source
===================================================================
--- source 2008-04-17 20:13:10 UTC (rev 1450)
+++ source 2008-04-17 21:15:45 UTC (rev 1451)
@@ -443,7 +443,7 @@
<p>Some conformance requirements are phrased as requirements on
elements, attributes, methods or objects. Such requirements fall
into two categories; those describing content model restrictions,
- and those describing implementation behaviour. The former category
+ and those describing implementation behavior. The former category
of requirements are requirements on documents and authoring
tools. The second category are requirements on user agents.</p>
@@ -866,7 +866,7 @@
documents</dfn> unless they are flagged as being <dfn>HTML
documents</dfn> when they are created. Whether a document is an
<span title="HTML documents">HTML document</span> or an <span
- title="XML documents">XML document</span> affects the behaviour of
+ title="XML documents">XML document</span> affects the behavior of
certain APIs, as well as a few CSS rendering rules. <a
href="#refsCSS21">[CSS21]</a></p>
@@ -910,8 +910,8 @@
attribute DOMString <span title="dom-document-dir">dir</span>;
attribute <span>HTMLElement</span> <span title="dom-document-body">body</span>;
readonly attribute <span>HTMLCollection</span> <span title="dom-document-images">images</span>;
-<!-- readonly attribute <span>HTMLCollection</span> <span title="dom-document-applets">applets</span>;
---> readonly attribute <span>HTMLCollection</span> <span title="dom-document-links">links</span>;
+ readonly attribute <span>HTMLCollection</span> <span title="dom-document-embeds">embeds</span>;
+ readonly attribute <span>HTMLCollection</span> <span title="dom-document-links">links</span>;
readonly attribute <span>HTMLCollection</span> <span title="dom-document-forms">forms</span>;
readonly attribute <span>HTMLCollection</span> <span title="dom-document-anchors">anchors</span>;
NodeList <span title="dom-document-getElementsByName">getElementsByName</span>(in DOMString elementName);
@@ -1526,7 +1526,7 @@
attribute must return the number of nodes <span>represented by the
collection</span>.</p>
- <p>On setting, the behaviour depends on whether the new value is
+ <p>On setting, the behavior depends on whether the new value is
equal to, greater than, or less than the number of nodes
<span>represented by the collection</span> at that time. If the
number is the same, then setting the attribute must do nothing. If
@@ -1936,6 +1936,11 @@
<code>Document</code> node, whose filter matches only
<code>img</code> elements.</p>
+ <p>The <dfn title="dom-document-embeds"><code>embeds</code></dfn>
+ attribute must return an <code>HTMLCollection</code> rooted at the
+ <code>Document</code> node, whose filter matches only
+ <code>embed</code> elements.</p>
+
<p>The <dfn title="dom-document-links"><code>links</code></dfn>
attribute must return an <code>HTMLCollection</code> rooted at the
<code>Document</code> node, whose filter matches only <code>a</code>
@@ -2052,7 +2057,7 @@
else on XML documents and XML elements. Is the sanity worth the
migration pain?</p>
- <p>Because these APIs interact with the parser, their behaviour
+ <p>Because these APIs interact with the parser, their behavior
varies depending on whether they are used with <span>HTML
documents</span> (and the <span>HTML parser</span>) or XHTML in
<span>XML documents</span> (and the <span>XML parser</span>). The
@@ -4571,7 +4576,7 @@
<h5>Metadata content</h5>
<p><dfn>Metadata content</dfn> is content that sets up the
- presentation or behaviour of the rest of the content, or that sets
+ presentation or behavior of the rest of the content, or that sets
up the relationship of the document with other documents, or that
conveys other "out of band" information.</p>
@@ -5257,7 +5262,7 @@
attributes are ignored and any associated CSS dropped, the page is
still usable.</p>
- <p>User agents must not derive any implementation behaviour from
+ <p>User agents must not derive any implementation behavior from
these attributes or values. Specifications intended for user agents
must not define these attributes to have any meaningful values.</p>
@@ -5755,7 +5760,7 @@
hyperlinks). User agents should process the links on a per-link
basis, not a per-element basis.</p>
- <p>The exact behaviour for links to external resources depends on
+ <p>The exact behavior for links to external resources depends on
the exact relationship, as defined for the relevant link type. Some
of the attributes control whether or not the external resource is to
be applied (as defined below). For external resources that are
@@ -12257,7 +12262,7 @@
<!-- XXX
make it an interactive element
- default activation behaviour is to do the play() if paused, pause()
+ default activation behavior is to do the play() if paused, pause()
otherwise
-->
@@ -15448,7 +15453,7 @@
> and the implementations need to make sure they handle any edge cases
> that the underlying graphics library does differently. (SVG Tiny 1.2
> appears to skip some of the problems by leaving things undefined and
-> allowing whatever behaviour the graphics library has.)
+> allowing whatever behavior the graphics library has.)
-->
@@ -15717,7 +15722,7 @@
title="">x1</var>, <var title="">y1</var>, <var title="">x2</var>,
<var title="">y2</var>, <var title="">radius</var>)</code></dfn>
method must do nothing if the context has no subpaths. If the
- context <em>does</em> have a subpath, then the behaviour depends on
+ context <em>does</em> have a subpath, then the behavior depends on
the arguments and the last point in the subpath.</p>
<p>Negative values for <var title="">radius</var> must cause the
@@ -17325,7 +17330,7 @@
those elements whose parent is a <code>tfoot</code> element, still
in tree order.</p>
- <p>The behaviour of the <dfn
+ <p>The behavior of the <dfn
title="dom-table-insertRow"><code>insertRow(<var
title="">index</var>)</code></dfn> method depends on the state of
the table. When it is called, the method must act as required by the
@@ -20474,7 +20479,7 @@
title="dom-datagrid-data">data</code> attribute is null. It must act
as described in this section.</p>
- <p>The behaviour of the default data provider depends on the nature
+ <p>The behavior of the default data provider depends on the nature
of the first element child of the <code>datagrid</code>.</p>
<dl class="switch">
@@ -21555,7 +21560,7 @@
<p>The exact algorithm used to populate the data grid is not defined
here, since it will differ based on the presentation used. However,
- the behaviour of user agents must be consistent with the
+ the behavior of user agents must be consistent with the
descriptions above. For example, it would be non-conformant for a
user agent to make cells have both a checkbox and be editable, as
the descriptions above state that cells that have a checkbox cannot
@@ -21667,7 +21672,7 @@
<p>If a cell is a cell whose value <a href="#cellType1">can be
cycled between multiple states</a>, then the user must be able to
activate the cell to cycle its value. When the user activates this
- "cycling" behaviour of a cell, then the <code>datagrid</code> must
+ "cycling" behavior of a cell, then the <code>datagrid</code> must
invoke the data provider's <code
title="dom-provider-cycleCell">cycleCell()</code> method, with a
<code>RowSpecification</code> object representing the cell's row as
@@ -22013,7 +22018,7 @@
content attributes.</p>
<p>The <dfn title="dom-command-click"><code>click()</code></dfn>
- method's behaviour depends on the value of the <code
+ method's behavior depends on the value of the <code
title="attr-command-type">type</code> attribute of the element, as
follows:</p>
@@ -22279,7 +22284,7 @@
<p>The list corresponding to a particular <code>menu</code> element
is built by iterating over its child nodes. For each child node in
- <span>tree order</span>, the required behaviour depends on what the
+ <span>tree order</span>, the required behavior depends on what the
node is, as follows:</p>
<dl class="switch">
@@ -22923,7 +22928,7 @@
otherwise.</p>
<p>The <span title="command-facet-Action">Action</span> of the
- command is to invoke the behaviour described in the definition of
+ command is to invoke the behavior described in the definition of
the <code title="dom-command-click">click()</code> method of the
<code>HTMLCommandElement</code> interface.</p> <!-- XXX update to
point to dom-click when we remove dom-command-click -->
@@ -27584,7 +27589,7 @@
reference.</p>
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
- should we do?: the behaviour depends on the context in which the
+ should we do?: the behavior depends on the context in which the
script that set the attribute is running. If the script ran as the
direct result of the execution of a <code>script</code> element in
the document represented by the <code>Location</code> object's
@@ -30322,7 +30327,7 @@
may be done in parallel with the primary request, and is independent
of the result of that request.</p>
- <p>User agents should allow the user to adjust this behaviour, for
+ <p>User agents should allow the user to adjust this behavior, for
example in conjunction with a setting that disables the sending of
HTTP <code title="">Referer</code> headers. Based on the user's
preferences, UAs may either <span>ignore</span> the <code
@@ -31721,7 +31726,7 @@
<p>If the caret is positioned somewhere where <span>phrasing
content</span> is not allowed (e.g. inside an empty <code>ol</code>
element), then the user agent must not insert the text directly at
- the caret position. In such cases the behaviour is UA-dependent,
+ the caret position. In such cases the behavior is UA-dependent,
but user agents must not, in response to a request to insert text,
generate a DOM that is less conformant than the DOM prior to the
request.</p>
@@ -31752,7 +31757,7 @@
action of a <code title="event-keydown">keydown</code> event whose
identifier is the "Enter" key and that has no modifiers set.</p>
- <p>The exact behaviour is UA-dependent, but user agents must not,
+ <p>The exact behavior is UA-dependent, but user agents must not,
in response to a request to break a paragraph, generate a DOM that
is less conformant than the DOM prior to the request.</p></dd>
@@ -31770,7 +31775,7 @@
<p>If the caret is positioned somewhere where <span>phrasing
content</span> is not allowed (e.g. in an empty <code>ol</code>
element), then the user agent must not insert the <code>br</code>
- element directly at the caret position. In such cases the behaviour
+ element directly at the caret position. In such cases the behavior
is UA-dependent, but user agents must not, in response to a request
to insert a line separator, generate a DOM that is less conformant
than the DOM prior to the request.</p></dd>
@@ -31791,7 +31796,7 @@
and deleting a <span title="the selection">selection</span> whose
start and end points do not share a common parent node.</p>
- <p>In any case, the exact behaviour is UA-dependent, but user
+ <p>In any case, the exact behavior is UA-dependent, but user
agents must not, in response to a request to delete text or an
element, generate a DOM that is less conformant than the DOM prior
to the request.</p></dd>
@@ -31823,7 +31828,7 @@
the user agent is sure that the user means to indicate
importance.</p>
- <p>The exact behaviour is UA-dependent, but user agents must not,
+ <p>The exact behavior is UA-dependent, but user agents must not,
in response to a request to wrap semantics around some text or to
insert or remove a semantic element, generate a DOM that is less
conformant than the DOM prior to the request.</p></dd>
@@ -32134,7 +32139,7 @@
model. Whenever the processing model described below causes one of
these events to be fired, the event fired must use the
<code>DragEvent</code> interface defined above, must have the
- bubbling and cancelable behaviours given in the table below, and
+ bubbling and cancelable behaviors given in the table below, and
must have the context information set up as described after the
table, with the <code title="dom-UIEvent-view">view</code> attribute
set to the view with which the user interacted to trigger the
@@ -33092,7 +33097,7 @@
changing.</p>
<p>The <dfn title="dom-UndoManager-add"><code>add(<var title="">data</var>,
- <var title="">title</var>)</code></dfn> method's behaviour depends on the
+ <var title="">title</var>)</code></dfn> method's behavior depends on the
current state. Normally, it must insert the <var title="">data</var> object
passed as an argument into the <span>undo transaction history</span>
immediately before the <span>undo position</span>, optionally
@@ -33849,7 +33854,7 @@
href="#contenteditable-wrapSemantic">be wrapped in the
semantics</a> of the <code>ol</code> element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
- — the exact behaviour is UA-defined).</dd>
+ — the exact behavior is UA-defined).</dd>
<dd><strong>Enabled When:</strong> The document is <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -33862,7 +33867,7 @@
href="#contenteditable-wrapSemantic">be wrapped in the
semantics</a> of the <code>ul</code> element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
- — the exact behaviour is UA-defined).</dd>
+ — the exact behavior is UA-defined).</dd>
<dd><strong>Enabled When:</strong> The document is <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -33954,7 +33959,7 @@
href="#contenteditable-wrapSemantic">be wrapped in the
semantics</a> of the <code>sup</code> element (or unwrapped, or, if
there is no selection, have that semantic inserted or removed
- — the exact behaviour is UA-defined).</dd>
+ — the exact behavior is UA-defined).</dd>
<dd><strong>Enabled When:</strong> The document is <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -34709,7 +34714,7 @@
method transmits data using the connection. If the connection is not
yet established, it must raise an <code>INVALID_STATE_ERR</code>
exception. If the connection <em>is</em> established, then the
- behaviour depends on the connection type, as described below.</p>
+ behavior depends on the connection type, as described below.</p>
<p>The <dfn
title="dom-Connection-disconnect"><code>disconnect()</code></dfn>
@@ -37561,16 +37566,16 @@
machine to a new state to <em>reconsume</em> the same character, or
switches it to a new state (to consume the next character), or
repeats the same state (to consume the next character). Some states
- have more complicated behaviour and can consume several characters
+ have more complicated behavior and can consume several characters
before switching to another state.</p>
- <p>The exact behaviour of certain states depends on a <dfn>content
+ <p>The exact behavior of certain states depends on a <dfn>content
model flag</dfn> that is set after certain tokens are emitted. The
flag has several states: <em title="">PCDATA</em>, <em
title="">RCDATA</em>, <em title="">CDATA</em>, and <em
title="">PLAINTEXT</em>. Initially it must be in the PCDATA
state. In the RCDATA and CDATA states, a further <dfn>escape
- flag</dfn> is used to control the behaviour of the tokeniser. It is
+ flag</dfn> is used to control the behavior of the tokeniser. It is
either true or false, and initially must be set to the false
state. The <span>insertion mode</span> and the <span>stack of open
elements</span> also affects tokenisation.</p>
@@ -37720,7 +37725,7 @@
<dd>
- <p>The behaviour of this state depends on the <span>content model
+ <p>The behavior of this state depends on the <span>content model
flag</span>.</p>
<dl>
@@ -38961,7 +38966,7 @@
state">in text</span> and <span title="entity in attribute value
state">in attributes</span>.</p>
- <p>The behaviour depends on the identity of the next character (the
+ <p>The behavior depends on the identity of the next character (the
one immediately after the U+0026 AMPERSAND character):</p>
<dl class="switch">
@@ -38987,7 +38992,7 @@
<p>Consume the U+0023 NUMBER SIGN.</p>
- <p>The behaviour further depends on the character after the U+0023
+ <p>The behavior further depends on the character after the U+0023
NUMBER SIGN:</p>
<dl class="switch">
@@ -43283,7 +43288,7 @@
- <h2 id="rendering">Rendering</h2>
+ <h2 id="rendering">Rendering and user-agent behavior</h2>
<!-- XXX
@@ -43332,7 +43337,7 @@
top border edge.</p> <!-- XXX horiz pos given bidi, and not
scrolling when not required to? -->
-<!-- Elements that have been dropped: ACRONYM APPLET B BASEFONT BLINK
+<!-- Elements that have been dropped: ACRONYM B BASEFONT BLINK
BIG CENTER DIR DIV FONT FRAME FRAMESET I ISINDEX MARQUEE NOEMBED
NOFRAMES S SPACER STRIKE TT U -->
@@ -43426,9 +43431,31 @@
+ <h3>Obsolete elements</h3>
+ <h4>The <dfn><code>applet</code></dfn> element</h4>
+ <p>The <code>applet</code> element is a Java-specific variant of the
+ <code>embed</code> element. In HTML5 the <code>applet</code> element
+ is obsoleted so that all extension frameworks (Java, .NET, Flash,
+ etc) are handled in a consistent manner.</p>
+ <p class="big-issue">define how the element works, if supported</p>
+
+ <pre class="idl">[XXX=HTMLDocument] interface {
+ readonly attribute <span>HTMLCollection</span> <span title="dom-document-applets">applets</span>;
+};</pre>
+
+ <p>The <dfn title="dom-document-applets"><code>applets</code></dfn>
+ attribute must return an <code>HTMLCollection</code> rooted at the
+ <code>Document</code> node, whose filter matches only
+ <code>applet</code> elements.</p>
+
+
+
+
+
+
<h2 id="no">Things that you can't do with this specification because
they are better handled using other technologies that are further
described herein</h2>
@@ -43549,6 +43576,7 @@
+
<h2 class="no-num" id="references">References</h2>
<p class="big-issue">This section will be written in a future
@@ -43700,7 +43728,7 @@
> I have use cases for both...I have a more desperate business need for
> the latter (and have build apps using the gross APIs out there today)
> but there are a lot of circumstances where an editor that already has
-> all standard HTML editing behaviour would be fine.
+> all standard HTML editing behavior would be fine.
>
- Paul Prescod
@@ -44813,9 +44841,9 @@
analogous way. If the element is on the right of the page, the menu
should drop to the left, and vice versa.</p>
- <p>UAs should implement the drop-down behaviour in more
+ <p>UAs should implement the drop-down behavior in more
platform-appropriate ways if the platform conventions differ from
- the behaviour described above.</p>
+ the behavior described above.</p>
More information about the Commit-Watchers
mailing list