- From: poot <cvsmail@w3.org>
- Date: Fri, 12 Sep 2008 14:10:23 +0900 (JST)
- To: public-html-diffs@w3.org
WF2: Begin to define how to handle enctype, action, method, and target
attributes. (whatwg r2165)
sandboxed navigation browsing context flag
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#sandboxed
End tags
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#end-tags0
Checked State
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#checked3
HTMLAnchorElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#htmlanchorelement
Post to data:
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#post-to
delete
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#delete0
4.10 Scripting
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#scripting1
4.9.14 Attributes for form submission
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#attributes2
4.11.6.5. Using the command element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using3
4.11.6.2. Using the button element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using0
4.11.6.3. Using the input element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using1
4.11.6.6. Using the bb element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using4
area
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#area
Get action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#get-action
Start tags
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#start7
Submit as entity body
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#submit
enctype
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#enctype0
enctype
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#enctype1
href
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#href6
Attribute names
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#attribute3
rectangle state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#rectangle0
method
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#method
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#value8
Mutate action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#mutate
4.11.6.4. Using the option element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using2
application/x-www-form-urlencoded encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#applicationx-www-form-urlencoded
createLink
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#createlink
method
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#method0
method
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#method1
4.9.16 Form submission
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#form-submission
action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#action1
action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#action0
Action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#action2
Constructing the form data set. For each element field in controls, in tree order, run the following substeps: If any of the following conditions are met, then skip these substeps for this element: The field element has a datalist element ancestor. The field element is disabled. The field element is a button but it is not submitter. The field element is an input element whose type attribute is in the Checkbox state and the control is not checked. The field element is an input element whose type attribute is in the Radio Button state and the control is not checked. The field element is an input element whose type attribute is in the File Upload state but the control does not have any files selected. Otherwise, process field as follows: If the field element is an input element whose type attribute is in the Image Button state, then run these further nested substeps: If the field element has an name attribute specified and value is not the empty string, let name be that value followed by a single U+002E FULL SOP (.) character. Otherwise, let name be the empty string. Let namex be the string consisting of the concatenation of name and a single U+0078 LATIN SMALL LETTER X (x) character. Let namey be the string consisting of the concatenation of name and a single U+0079 LATIN SMALL LETTER Y (y) character. The field element is submitter, and before this algorithm was invoked the user indicated a coordinate. Let x be the x-component of the coordindate selected by the user, and let y be the y-component of the coordinate selected by the user. Append an entry in the form data set with the name namex and the value x. Append an entry in the form data set with the name namey and the value y. Skip the remaining substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. If the field element does not have a name attribute specified, or its name attribute's value is the empty strig, skip these substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. Let name be the value of the field element's name attribute. If the field element is a select element, then for each option element in the select element that is selected, append an entry in the form data set with the name as the name and the value of the option element as the value. Otherwise, if the field element is an input element whose type attribute is in the File Upload state, then for each file selected in the input element, append an entry in the form data set with the name as the name and the file as the value. (Both the file name and the file contents are subsequently used.) Otherwise, append an entry in the form data set with name as the name and the value of the field element as the value.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#constructing-form-data-set
target
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#target6
4.11.6.1. Using the a element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#using
target
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#target4
target
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#target5
target
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#target3
enctype
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#enctype
a
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#a
8.1.2.3. Attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#attributes3
Attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#attributes4
4.9.15 Constraint validation
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#constraint
Put to data:
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#put-to
contextmenu
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#contextmenu
submitted
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#submitted
Following hyperlinks
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#following0
disabled
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#disabled4
Mail with headers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#mail-with
action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#action
Mail as body
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#mail-as
checked
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#checked4
click()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#click0
Delete action
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1338.html#delete
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1337&r2=1.1338&f=h
http://html5.org/tools/web-apps-tracker?from=2164&to=2165
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1337
retrieving revision 1.1338
diff -u -d -r1.1337 -r1.1338
--- Overview.html 11 Sep 2008 22:16:57 -0000 1.1337
+++ Overview.html 12 Sep 2008 01:01:57 -0000 1.1338
@@ -27,7 +27,7 @@
for HTML and XHTML</h2>
<h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
- Editor's Draft <!--ZZZ-->11 September 2008</h2>
+ Editor's Draft <!--ZZZ-->12 September 2008</h2>
<dl><!-- ZZZ: update the month/day
<dt>This Version:</dt>
@@ -199,7 +199,7 @@
<p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
the W3C working group responsible for this specification's progress along
- the W3C Recommendation track. <!--ZZZ:--> This specification is the 11
+ the W3C Recommendation track. <!--ZZZ:--> This specification is the 12
September 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
<!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
<!-- relationship to other work (required) -->
@@ -1070,10 +1070,13 @@
<li><a href="#attributes1"><span class=secno>4.9.13 </span>Attributes
common to form controls</a>
- <li><a href="#constraint"><span class=secno>4.9.14 </span>Constraint
+ <li><a href="#attributes2"><span class=secno>4.9.14 </span>Attributes
+ for form submission</a>
+
+ <li><a href="#constraint"><span class=secno>4.9.15 </span>Constraint
validation</a>
- <li><a href="#form-submission"><span class=secno>4.9.15 </span>Form
+ <li><a href="#form-submission"><span class=secno>4.9.16 </span>Form
submission</a>
</ul>
@@ -1863,7 +1866,7 @@
<li><a href="#end-tags"><span class=secno>8.1.2.2. </span>End
tags</a>
- <li><a href="#attributes2"><span class=secno>8.1.2.3.
+ <li><a href="#attributes3"><span class=secno>8.1.2.3.
</span>Attributes</a>
<li><a href="#optional"><span class=secno>8.1.2.4. </span>Optional
@@ -13092,7 +13095,7 @@
<dd><code title=attr-hyperlink-href><a href="#href6">href</a></code>
- <dd><code title=attr-hyperlink-target><a href="#target3">target</a></code>
+ <dd><code title=attr-hyperlink-target><a href="#target6">target</a></code>
<dd><code title=attr-hyperlink-ping><a href="#ping">ping</a></code>
@@ -13134,7 +13137,7 @@
placed, if it had been relevant.
<p>The <code title=attr-hyperlink-target><a
- href="#target3">target</a></code>, <code title=attr-hyperlink-ping><a
+ href="#target6">target</a></code>, <code title=attr-hyperlink-ping><a
href="#ping">ping</a></code>, <code title=attr-hyperlink-rel><a
href="#rel3">rel</a></code>, <code title=attr-hyperlink-media><a
href="#media14">media</a></code>, <code title=attr-hyperlink-hreflang><a
@@ -13162,7 +13165,7 @@
title="following hyperlinks">follow hyperlinks</a> created using the
<code><a href="#a">a</a></code> element. The <code
title=attr-hyperlink-href><a href="#href6">href</a></code>, <code
- title=attr-hyperlink-target><a href="#target3">target</a></code> and <code
+ title=attr-hyperlink-target><a href="#target6">target</a></code> and <code
title=attr-hyperlink-ping><a href="#ping">ping</a></code> attributes
decide how the link is followed. The <code title=attr-hyperlink-rel><a
href="#rel3">rel</a></code>, <code title=attr-hyperlink-media><a
@@ -13183,7 +13186,7 @@
a <code title=dom-click><a href="#click1">click()</a></code> method call
was the reason for the event being dispatched), and the <code><a
href="#a">a</a></code> element's <code title=attr-hyperlink-target><a
- href="#target3">target</a></code> attribute is <span
+ href="#target6">target</a></code> attribute is <span
class=big-issue>...</span> then raise an <code>INVALID_ACCESS_ERR</code>
exception and abort these steps.
@@ -17344,7 +17347,7 @@
<p>This flag also <a href="#sandboxWindowOpen">prevents content from
creating new auxiliary browsing contexts</a>, e.g. using the <code
- title=attr-hyperlink-target><a href="#target3">target</a></code>
+ title=attr-hyperlink-target><a href="#target6">target</a></code>
attribute or the <code title=dom-open><a
href="#open2">window.open()</a></code> method.</p>
@@ -24014,7 +24017,7 @@
<dd><code title=attr-hyperlink-href><a href="#href6">href</a></code>
- <dd><code title=attr-hyperlink-target><a href="#target3">target</a></code>
+ <dd><code title=attr-hyperlink-target><a href="#target6">target</a></code>
<dd><code title=attr-hyperlink-ping><a href="#ping">ping</a></code>
@@ -24195,7 +24198,7 @@
hyperlinks">follow hyperlinks</a> created using the <code><a
href="#area">area</a></code> element, as described in the next section,
the <code title=attr-hyperlink-href><a href="#href6">href</a></code>,
- <code title=attr-hyperlink-target><a href="#target3">target</a></code> and
+ <code title=attr-hyperlink-target><a href="#target6">target</a></code> and
<code title=attr-hyperlink-ping><a href="#ping">ping</a></code> attributes
decide how the link is followed. The <code title=attr-hyperlink-rel><a
href="#rel3">rel</a></code>, <code title=attr-hyperlink-media><a
@@ -24206,7 +24209,7 @@
before the user follows the link.
<p>The <code title=attr-hyperlink-target><a
- href="#target3">target</a></code>, <code title=attr-hyperlink-ping><a
+ href="#target6">target</a></code>, <code title=attr-hyperlink-ping><a
href="#ping">ping</a></code>, <code title=attr-hyperlink-rel><a
href="#rel3">rel</a></code>, <code title=attr-hyperlink-media><a
href="#media14">media</a></code>, <code title=attr-hyperlink-hreflang><a
@@ -27434,11 +27437,60 @@
<p class=big-issue>... <dfn id=value8 title=concept-fe-value>value</dfn>
- <h4 id=constraint><span class=secno>4.9.14 </span>Constraint validation</h4>
+ <h4 id=attributes2><span class=secno>4.9.14 </span>Attributes for form
+ submission</h4>
+
+ <p class=big-issue>... <dfn id=action title=attr-fs-action>action</dfn>
+ content attribute
+
+ <p class=big-issue>... <dfn id=action0 title=dom-fs-action>action</dfn> DOM
+ attribute
+
+ <p class=big-issue>... <dfn id=action1 title=concept-fs-action>action</dfn>
+ if present else form's else default
+
+ <p class=big-issue>... <dfn id=method title=attr-fs-method>method</dfn>
+ content attribute
+
+ <p class=big-issue>... <dfn id=method0 title=dom-fs-method>method</dfn> DOM
+ attribute
+
+ <p class=big-issue>... <dfn id=method1 title=concept-fs-method>method</dfn>
+ if present else form's else default
+
+ <p class=big-issue>... <dfn id=enctype title=attr-fs-enctype>enctype</dfn>
+ content attribute
+
+ <p class=big-issue>... <dfn id=enctype0 title=dom-fs-enctype>enctype</dfn>
+ DOM attribute
+
+ <p class=big-issue>... <dfn id=enctype1
+ title=concept-fs-enctype>enctype</dfn> if present else form's else default
+
+ <p class=big-issue>... <dfn id=target3 title=attr-fs-target>target</dfn>
+ content attribute
+
+ <p class=big-issue>... <dfn id=target4 title=dom-fs-target>target</dfn> DOM
+ attribute
+
+ <p class=big-issue>... <dfn id=target5 title=concept-fs-target>target</dfn>
+ if present else form's else base target else default</p>
+ <!-- c.f. hyperlink following -->
+
+ <p>Attributes for form submission can be specified both on <code><a
+ href="#form">form</a></code> elements and on elements that represent
+ buttons that submit forms, e.g. an <code><a
+ href="#input0">input</a></code> element whose <code
+ title=attr-input-type>type</code> attribute is in the <span
+ title=attr-input-type-submit-state>Submit Button</span> state. The
+ attributes on the buttons, when omitted, default to the values given on
+ the corresponding the <code><a href="#form">form</a></code> element.
+
+ <h4 id=constraint><span class=secno>4.9.15 </span>Constraint validation</h4>
<p class=big-issue>...
- <h4 id=form-submission><span class=secno>4.9.15 </span>Form submission</h4>
+ <h4 id=form-submission><span class=secno>4.9.16 </span>Form submission</h4>
<p>When a form <var title="">form</var> is <dfn id=submitted
title=concept-form-submit>submitted</dfn> from an element <var
@@ -27624,7 +27676,216 @@
</ol>
<li>
+ <p>Let <var title="">action</var> be the <var title="">submitter</var>
+ element's <a href="#action1" title=concept-fs-action>action</a>.
+
+ <li>
+ <p><a href="#resolve" title="resolve a url">Resolve</a> the <a
+ href="#url">URL</a> <var title="">action</var>. If this fails, abort
+ these steps.
+
+ <li>
+ <p>Let <var title="">scheme</var> be the <a href="#ltschemegt"
+ title=url-scheme><scheme></a> of the resulting <a
+ href="#absolute">absolute URL</a>.
+
+ <li>
+ <p>Let <var title="">enctype</var> be the <var title="">submitter</var>
+ element's <a href="#enctype1" title=concept-fs-enctype>enctype</a>.
+
+ <li>
+ <p>Let <var title="">method</var> be the <var title="">submitter</var>
+ element's <a href="#method1" title=concept-fs-method>method</a>.
+
+ <li>
+ <p>Let <var title="">target</var> be the <var title="">submitter</var>
+ element's <a href="#target5" title=concept-fs-target>target</a>.
+
+ <li>
+ <p>Select the appropriate row in the table below based on the value of
+ <var title="">scheme</var> as given by the first cell of each row. Then,
+ select the appropriate cell on that row based on the value of <var
+ title="">method</var> as given in the first cell of each column. Then,
+ jump to the steps named in that cell and defined below the table.</p>
+
+ <table>
+ <tbody>
+ <tr>
+ <td>
+
+ <th> GET
+
+ <th> POST
+
+ <th> PUT
+
+ <th> DELETE
+
+ <tr>
+ <th> <code title="">http</code>
+
+ <td> <a href="#mutate" title=submit-mutate-action>Mutate action</a>
+
+ <td> <a href="#submit" title=submit-body>Submit as entity body</a>
+
+ <td> <a href="#submit" title=submit-body>Submit as entity body</a>
+
+ <td> <a href="#delete" title=submit-delete-action>Delete action</a>
+
+ <tr>
+ <th> <code title="">https</code>
+
+ <td> <a href="#mutate" title=submit-mutate-action>Mutate action</a>
+
+ <td> <a href="#submit" title=submit-body>Submit as entity body</a>
+
+ <td> <a href="#submit" title=submit-body>Submit as entity body</a>
+
+ <td> <a href="#delete" title=submit-delete-action>Delete action</a>
+
+ <tr>
+ <th> <code title="">ftp</code>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <tr>
+ <th> <code title="">javascript</code>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <tr>
+ <th> <code title="">data</code>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <td> <a href="#post-to" title=submit-data-post>Post to data:</a>
+
+ <td> <a href="#put-to" title=submit-data-put>Put to data:</a>
+
+ <td> <a href="#get-action" title=submit-get-action>Get action</a>
+
+ <tr>
+ <th> <code title="">mailto</code>
+
+ <td> <a href="#mail-with" title=submit-mailto-headers>Mail with
+ headers</a>
+
+ <td> <a href="#mail-as" title=submit-mailto-body>Mail as body</a>
+
+ <td> <a href="#mail-with" title=submit-mailto-headers>Mail with
+ headers</a>
+
+ <td> <a href="#mail-with" title=submit-mailto-headers>Mail with
+ headers</a>
+ </table>
+
+ <p>If <var title="">scheme</var> is not one of those listed in this
+ table, then the behavior is not defined by this specification. User
+ agents should, in the absence of another specification defining this,
+ act in a manner analogous to that defined in this specification for
+ similar schemes.</p>
+
+ <p>The behaviors are as follows:</p>
+
+ <dl class=switch>
+ <dt><dfn id=mutate title=submit-mutate-action>Mutate action</dfn>
+
+ <dd>
+ <p>Let <var title="">query</var> be the resulting encoding the <var
+ title="">form data set</var> using the <a
+ href="#applicationx-www-form-urlencoded"><code
+ title="">application/x-www-form-urlencoded</code> encoding
+ algorithm</a>.</p>
+
+ <p>Let <var title="">destination</var> be a new <a href="#url">URL</a>
+ that is equal to the <var title="">action</var> except that its <a
+ href="#ltquerygt" title=url-query><query></a> component is
+ replaced by <var title="">query</var> (adding a U+003F QUESTION MARK
+ (?) character if appropriate).</p>
+
+ <p>If the user indicated a specific <a href="#browsing1">browsing
+ context</a> to use when submitting the form, then let <var
+ title="">target browsing context</var> be that <a
+ href="#browsing1">browsing context</a>.</p>
+
+ <p>Otherwise, apply <a href="#the-rules">the rules for choosing a
+ browsing context given a browsing context name</a> using <var
+ title="">target</var> as the name and the <a
+ href="#browsing1">browsing context</a> of <var title="">form</var> as
+ the context in which the algorithm is executed, and let <var
+ title="">target browsing context</var> be the resulting <a
+ href="#browsing1">browsing context</a>.</p>
+
+ <p><a href="#navigate">Navigate</a> <var title="">target browsing
+ context</var> to <var title="">destination</var>. If <var
+ title="">target browsing context</var> was newly created for this
+ purpose by the steps above, then it must be navigated with <a
+ href="#replacement">replacement enabled</a>.</p>
+
+ <dt><dfn id=submit title=submit-body>Submit as entity body</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=delete title=submit-delete-action>Delete action</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=get-action title=submit-get-action>Get action</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=post-to title=submit-data-post>Post to data:</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=put-to title=submit-data-put>Put to data:</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=mail-with title=submit-mailto-headers>Mail with
+ headers</dfn>
+
+ <dd>
+ <p class=big-issue>...
+
+ <dt><dfn id=mail-as title=submit-mailto-body>Mail as body</dfn>
+
+ <dd>
+ <p class=big-issue>...
+ </dl>
+
+ <li>
+ <p class=big-issue>...
+ </ol>
+
+ <p>The <dfn id=applicationx-www-form-urlencoded><code
+ title="">application/x-www-form-urlencoded</code> encoding algorithm</dfn>
+ is as follows:
+
+ <ol>
+ <li>
<p class=big-issue>...
+ </li>
+ <!-- During this step, the form data set is examined to ensure all
+ the characters are representable in the submission character
+ encoding. -->
</ol>
<h3 id=scripting1><span class=secno>4.10 </span>Scripting</h3>
@@ -31409,7 +31670,7 @@
<p>If the user selects a menu item that represents a <span
title=concept-commands>command</span>, then the UA must invoke that
- command's <a href="#action" title=command-facet-Action>Action</a>.
+ command's <a href="#action2" title=command-facet-Action>Action</a>.
<p>Context menus must not, while being shown, reflect changes in the DOM;
they are constructed as the default action of the <code
@@ -31502,7 +31763,7 @@
<dd>Whether the command is checked or not.
- <dt><dfn id=action title=command-facet-Action>Action</dfn>
+ <dt><dfn id=action2 title=command-facet-Action>Action</dfn>
<dd>The actual effect that triggering the command will have. This could be
a scripted event handler, a <a href="#url">URL</a> to which to <a
@@ -31630,7 +31891,7 @@
href="#command0">command</a></code> elements.
<p>The <dfn id=click0 title=dom-command-ro-click><code>click()</code></dfn>
- method must trigger the <a href="#action"
+ method must trigger the <a href="#action2"
title=command-facet-Action>Action</a> for the command. If the element does
not define a command, this method must do nothing. This method will be
shadowed by the <code title=dom-click><a href="#click1">click()</a></code>
@@ -31704,7 +31965,7 @@
<p>The <a href="#checked3" title=command-facet-CheckedState>Checked
State</a> of the command is always false. (The command is never checked.)
- <p>The <a href="#action" title=command-facet-Action>Action</a> of the
+ <p>The <a href="#action2" title=command-facet-Action>Action</a> of the
command is to <a href="#firing" title="fire a click event">fire a <code
title="">click</code> event</a> at the element.
@@ -31721,7 +31982,7 @@
title=command-facet-Hint>Hint</a>, <a href="#icon1"
title=command-facet-Icon>Icon</a>, <a href="#hidden"
title=command-facet-HiddenState>Hidden State</a>, <a href="#checked3"
- title=command-facet-CheckedState>Checked State</a>, and <a href="#action"
+ title=command-facet-CheckedState>Checked State</a>, and <a href="#action2"
title=command-facet-Action>Action</a> facets of the command are determined
<a href="#using5" title=a-command>as for <code>a</code> elements</a> (see
the previous section).
@@ -31803,7 +32064,7 @@
has a <code title=attr-input-checked>checked</code> attribute, and false
otherwise.
- <p>The <a href="#action" title=command-facet-Action>Action</a> of the
+ <p>The <a href="#action2" title=command-facet-Action>Action</a> of the
command is to <a href="#firing" title="fire a click event">fire a <code
title="">click</code> event</a> at the element.</p>
<!-- XXX this
@@ -31860,7 +32121,7 @@
title=dom-option-selected>selected</code> DOM attribute is true, and false
otherwise.
- <p>The <a href="#action" title=command-facet-Action>Action</a> of the
+ <p>The <a href="#action2" title=command-facet-Action>Action</a> of the
command depends on its <a href="#type19"
title=command-facet-Type>Type</a>. If the command is of <a href="#type19"
title=command-facet-Type>Type</a> "radio" then this must set the <code
@@ -31924,7 +32185,7 @@
title=attr-command-checked><a href="#checked1">checked</a></code>
attribute, and false otherwise.
- <p>The <a href="#action" title=command-facet-Action>Action</a> of the
+ <p>The <a href="#action2" title=command-facet-Action>Action</a> of the
command is to invoke the behavior described in the definition of the <code
title=dom-command-click><a href="#click">click()</a></code> method of the
<code><a href="#htmlcommandelement">HTMLCommandElement</a></code>
@@ -31990,7 +32251,7 @@
<p>The <a href="#checked3" title=command-facet-CheckedState>Checked
State</a> of the command is always false. (The command is never checked.)
- <p>The <a href="#action" title=command-facet-Action>Action</a> of the
+ <p>The <a href="#action2" title=command-facet-Action>Action</a> of the
command is to perform the <i>action</i> of the <code><a
href="#bb">bb</a></code> element's <code title=attr-bb-type><a
href="#type15">type</a></code> attribute's state.
@@ -39828,7 +40089,7 @@
element.</p>
</div>
- <p>The <dfn id=target3
+ <p>The <dfn id=target6
title=attr-hyperlink-target><code>target</code></dfn> attribute, if
present, must be a <a href="#valid10">valid browsing context name or
keyword</a>. User agents use this name when <a
@@ -39891,22 +40152,23 @@
hyperlink must further have its <var><a href="#hyperlink2">hyperlink
suffix</a></var> appended to it.
- <p>If the user indicated a specific browsing context when following the
- hyperlink, or if the user agent is configured to follow hyperlinks by
- navigating a particular browsing context, then that must be the browsing
- context that is navigated.
+ <p>If the user indicated a specific <a href="#browsing1">browsing
+ context</a> when following the hyperlink, or if the user agent is
+ configured to follow hyperlinks by navigating a particular browsing
+ context, then that must be the <a href="#browsing1">browsing context</a>
+ that is navigated.
<p>Otherwise, if the hyperlink element is an <code><a
href="#a">a</a></code> or <code><a href="#area">area</a></code> element
that has a <code title=attr-hyperlink-target><a
- href="#target3">target</a></code> attribute, then the browsing context
- that is navigated must be chosen by applying <a href="#the-rules">the
- rules for choosing a browsing context given a browsing context name</a>,
- using the value of the <code title=attr-hyperlink-target><a
- href="#target3">target</a></code> attribute as the browsing context name.
- If these rules result in the creation of a new <a
- href="#browsing1">browsing context</a>, it must be navigated with <a
- href="#replacement">replacement enabled</a>.
+ href="#target6">target</a></code> attribute, then the <a
+ href="#browsing1">browsing context</a> that is navigated must be chosen by
+ applying <a href="#the-rules">the rules for choosing a browsing context
+ given a browsing context name</a>, using the value of the <code
+ title=attr-hyperlink-target><a href="#target6">target</a></code> attribute
+ as the browsing context name. If these rules result in the creation of a
+ new <a href="#browsing1">browsing context</a>, it must be navigated with
+ <a href="#replacement">replacement enabled</a>.
<p>Otherwise, if the hyperlink element is a <a href="#sidebar0"
title=rel-sidebar-hyperlink>sidebar hyperlink</a> and the user agent
@@ -39917,7 +40179,7 @@
<p>Otherwise, if the hyperlink element is an <code><a
href="#a">a</a></code> or <code><a href="#area">area</a></code> element
with no <code title=attr-hyperlink-target><a
- href="#target3">target</a></code> attribute, but one of the child nodes of
+ href="#target6">target</a></code> attribute, but one of the child nodes of
<a href="#the-head0">the <code>head</code> element</a> is a <code><a
href="#base">base</a></code> element with a <code
title=attr-base-target><a href="#target">target</a></code> attribute, then
@@ -43800,7 +44062,7 @@
<dd><strong>Value:</strong> Always the string "<code
title="">false</code>".
- <dt><dfn id=delete title=command-delete><code>delete</code></dfn>
+ <dt><dfn id=delete0 title=command-delete><code>delete</code></dfn>
<dd><strong>Action:</strong> The user agent must act as if the user had
performed <a href="#contenteditable-delete">a backspace operation</a>.
@@ -46678,13 +46940,13 @@
characters</a>.
<li>Then, the start tag may have a number of attributes, the <a
- href="#attributes3" title=syntax-attributes>syntax for which</a> is
+ href="#attributes4" title=syntax-attributes>syntax for which</a> is
described below. Attributes may be separated from each other by one or
more <a href="#space" title="space character">space characters</a>.
<li>After the attributes, there may be one or more <a href="#space"
title="space character">space characters</a>. (Some attributes are
- required to be followed by a space. See the <a href="#attributes3"
+ required to be followed by a space. See the <a href="#attributes4"
title=syntax-attributes>attributes section</a> below.)
<li>Then, if the element is one of the <a href="#void-elements">void
@@ -46719,9 +46981,9 @@
(<code>></code>) character.
</ol>
- <h5 id=attributes2><span class=secno>8.1.2.3. </span>Attributes</h5>
+ <h5 id=attributes3><span class=secno>8.1.2.3. </span>Attributes</h5>
- <p><dfn id=attributes3 title=syntax-attributes>Attributes</dfn> for an
+ <p><dfn id=attributes4 title=syntax-attributes>Attributes</dfn> for an
element are expressed inside the element's start tag.
<p>Attributes have a name and a value. <dfn id=attribute3
Received on Friday, 12 September 2008 05:11:02 UTC