- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 07 Oct 2008 21:28:46 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20022
Modified Files:
Overview.html
Log Message:
The user is not a conformance class... (credit: sp) (whatwg r2294)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1466
retrieving revision 1.1467
diff -u -d -r1.1466 -r1.1467
--- Overview.html 7 Oct 2008 21:21:17 -0000 1.1466
+++ Overview.html 7 Oct 2008 21:28:44 -0000 1.1467
@@ -19577,7 +19577,7 @@
<code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> methods.<h6 id=e-mail-state><span class=secno>4.10.4.1.3 </span><dfn title=attr-input-type-email>E-mail</dfn> state</h6><p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#e-mail-state title=attr-input-type-email>E-mail</a> state, the rules in this
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for editing a
single e-mail address given in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the e-mail address
+ the user agent should allow the user to change the e-mail address
represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>. User
agents may allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not an
e-mail address. User agents should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string. User
@@ -19623,8 +19623,9 @@
<code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> methods.<h6 id=url-state><span class=secno>4.10.4.1.4 </span><dfn title=attr-input-type-url>URL</dfn> state</h6><p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#url-state title=attr-input-type-url>URL</a> state, the rules in this
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for editing a
single <a href=#url>URL</a> given in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>.<p>If the is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user
- should allow the user to change the URL represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>. User agents may allow the
- user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a
+ agent should allow the user to change the URL represented by its
+ <a href=#concept-fe-value title=concept-fe-value>value</a>. User agents may allow
+ the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string that is not a <a href=#valid-url>valid URL</a>. User agents should
allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string. User
agents must not allow users to insert U+000A LINE FEED (LF) or
@@ -19705,7 +19706,7 @@
string representing a specific <a href=#concept-datetime title=concept-datetime>UTC
date and time</a>. User agents may display the date and time in
whatever timezone is appropriate for the user.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-datetime title=concept-datetime>UTC date and time</a> represented by its
+ the user agent should allow the user to change the <a href=#concept-datetime title=concept-datetime>UTC date and time</a> represented by its
<a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-utc-date-and-time-string title="parse a UTC date and time string">parsing a UTC date and
time</a> from it. User agents must not allow the user to set the
<a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not
@@ -19781,7 +19782,7 @@
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for setting
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a specific <a href=#concept-date title=concept-date>date</a>.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-date title=concept-date>date</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-date-string title="parse a date string">parsing a date</a> from it. User
+ the user agent should allow the user to change the <a href=#concept-date title=concept-date>date</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-date-string title="parse a date string">parsing a date</a> from it. User
agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not a
<a href=#valid-date-string>valid date string</a>. If the user agent provides a user
interface for selecting a <a href=#concept-date title=concept-date>date</a>,
@@ -19859,7 +19860,7 @@
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for setting
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a specific <a href=#concept-month title=concept-month>month</a>.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-month title=concept-month>month</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-month-string title="parse a month string">parsing a month</a> from it. User
+ the user agent should allow the user to change the <a href=#concept-month title=concept-month>month</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-month-string title="parse a month string">parsing a month</a> from it. User
agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not a
<a href=#valid-month-string>valid month string</a>. If the user agent provides a user
interface for selecting a <a href=#concept-month title=concept-month>month</a>,
@@ -19935,7 +19936,7 @@
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for setting
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a specific <a href=#concept-week title=concept-week>week</a>.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-week title=concept-week>week</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-week-string title="parse a week string">parsing a week</a> from it. User
+ the user agent should allow the user to change the <a href=#concept-week title=concept-week>week</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-week-string title="parse a week string">parsing a week</a> from it. User
agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not a
<a href=#valid-week-string>valid week string</a>. If the user agent provides a user
interface for selecting a <a href=#concept-week title=concept-week>week</a>,
@@ -20013,7 +20014,7 @@
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for setting
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a specific <a href=#concept-time title=concept-time>time</a>.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-time title=concept-time>time</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-time-string title="parse a time string">parsing a time</a> from it. User
+ the user agent should allow the user to change the <a href=#concept-time title=concept-time>time</a> represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by <a href=#parse-a-time-string title="parse a time string">parsing a time</a> from it. User
agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not a
<a href=#valid-time-string>valid time string</a>. If the user agent provides a user
interface for selecting a <a href=#concept-time title=concept-time>time</a>,
@@ -20086,7 +20087,7 @@
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a <a href=#concept-datetime-local title=concept-datetime-local>local
date and time</a>, with no time zone information.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the <a href=#concept-datetime-local title=concept-datetime-local>date and time</a> represented by
+ the user agent should allow the user to change the <a href=#concept-datetime-local title=concept-datetime-local>date and time</a> represented by
its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained by
<a href=#parse-a-local-date-and-time-string title="parse a local date and time string">parsing a date and
time</a> from it. User agents must not allow the user to set the
@@ -20153,12 +20154,12 @@
this section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a control for setting
the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a
string representing a number.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the number represented by
- its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained from
- applying the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point number
- values</a> to it. User agents must not allow the user to set the
- <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not
- a <a href=#valid-floating-point-number>valid floating point number</a>. If the user agent
+ the user agent should allow the user to change the number
+ represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as
+ obtained from applying the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point
+ number values</a> to it. User agents must not allow the user to
+ set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that
+ is not a <a href=#valid-floating-point-number>valid floating point number</a>. If the user agent
provides a user interface for selecting a number, then the <a href=#concept-fe-value title=concept-fe-value>value</a> must be set to a <a href=#valid-floating-point-number>valid
floating point number</a> representing the user's selection. User
agents should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.<p><strong>The <a href=#value-sanitization-algorithm>value sanitization algorithm</a> is as
@@ -20220,12 +20221,12 @@
state.<p class=note>In this state, the range and step constraints are
enforced even during user input, and there is no way to set the
value to the empty string.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the number represented by
- its <a href=#concept-fe-value title=concept-fe-value>value</a>, as obtained from
- applying the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point number
- values</a> to it. User agents must not allow the user to set the
- <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not
- a <a href=#valid-floating-point-number>valid floating point number</a>. If the user agent
+ the user agent should allow the user to change the number
+ represented by its <a href=#concept-fe-value title=concept-fe-value>value</a>, as
+ obtained from applying the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point
+ number values</a> to it. User agents must not allow the user to
+ set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that
+ is not a <a href=#valid-floating-point-number>valid floating point number</a>. If the user agent
provides a user interface for selecting a number, then the <a href=#concept-fe-value title=concept-fe-value>value</a> must be set to a <a href=#valid-floating-point-number>valid
floating point number</a> representing the user's selection. User
agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.<p><strong>The <a href=#value-sanitization-algorithm>value sanitization algorithm</a> is as
@@ -20417,10 +20418,10 @@
section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a list of <dfn id=concept-input-type-file-selected title=concept-input-type-file-selected>selected files</dfn>, each
file consisting of a file name, a file type, and a file body (the
contents of the file).<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to change the files on the list,
- e.g. adding or removing files. Files can be from the filesystem or
- created on the fly, e.g. a picture taken from a camera connected to
- the user's device.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and the list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a> is
+ the user agent should allow the user to change the files on the
+ list, e.g. adding or removing files. Files can be from the
+ filesystem or created on the fly, e.g. a picture taken from a camera
+ connected to the user's device.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and the list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a> is
empty, then the element is <a href=#suffering-from-being-missing>suffering from being
missing</a>.<p>There must be no more than one file in the list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>.</p><hr><p>The <dfn id=attr-input-accept title=attr-input-accept><code>accept</code></dfn>
attribute may be specified to provide user agents with a hint of
@@ -20480,7 +20481,7 @@
activated, submits the form. If the element has a <code title=attr-input-value><a href=#attr-input-value>value</a></code> attribute, the button's label
must be the value of that attribute; otherwise, it must be an
implementation-defined string that means "Submit" or some such.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to activate the element.<p>The element's <a href=#activation-behavior>activation behavior</a>, if the element
+ the user agent should allow the user to activate the element.<p>The element's <a href=#activation-behavior>activation behavior</a>, if the element
has a <a href=#form-owner>form owner</a>, is to <a href=#concept-form-submit title=concept-form-submit>submit</a> the <a href=#form-owner>form
owner</a> from the <code><a href=#the-input-element>input</a></code> element; otherwise, it is
to do nothing.<p>The <code title=attr-fs-action><a href=#attr-fs-action>action</a></code>, <code title=attr-fs-enctype><a href=#attr-fs-enctype>enctype</a></code>, <code title=attr-fs-method><a href=#attr-fs-method>method</a></code>, and <code title=attr-fs-target><a href=#attr-fs-target>target</a></code> attributes control the form
@@ -20568,17 +20569,17 @@
to display that image, then: The element represents a control for
selecting a <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a> from
the image specified by the <code title=attr-input-src><a href=#attr-input-src>src</a></code>
- attribute; if the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user should allow the
- user to select this <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a>. The
+ attribute; if the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user agent should
+ allow the user to select this <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a>. The
<a href=#activation-behavior>activation behavior</a> in this case consists of taking the
user's selected <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>coordinate</a>, and
then, if the element has a <a href=#form-owner>form owner</a>, <a href=#concept-form-submit title=concept-form-submit>submitting</a> the <code><a href=#the-input-element>input</a></code>
element's <a href=#form-owner>form owner</a> from the <code><a href=#the-input-element>input</a></code>
element.<p>Otherwise, the element represents a submit button whose label is
given by the value of the <code title=attr-input-alt><a href=#attr-input-alt>alt</a></code>
- attribute; if the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user should allow the
- user to activate the button. The <a href=#activation-behavior>activation behavior</a> in
- this case consists of setting the <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>selected
+ attribute; if the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>, the user agent should
+ allow the user to activate the button. The <a href=#activation-behavior>activation
+ behavior</a> in this case consists of setting the <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>selected
coordinate</a> to (0,0), and then, if the element has a
<a href=#form-owner>form owner</a>, <a href=#concept-form-submit title=concept-form-submit>submitting</a> the <code><a href=#the-input-element>input</a></code>
element's <a href=#form-owner>form owner</a> from the <code><a href=#the-input-element>input</a></code>
@@ -20627,7 +20628,7 @@
activated, resets the form. If the element has a <code title=attr-input-value><a href=#attr-input-value>value</a></code> attribute, the button's label
must be the value of that attribute; otherwise, it must be an
implementation-defined string that means "Reset" or some such.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to activate the element.<p>The element's <a href=#activation-behavior>activation behavior</a>, if the element
+ the user agent should allow the user to activate the element.<p>The element's <a href=#activation-behavior>activation behavior</a>, if the element
has a <a href=#form-owner>form owner</a>, is to <a href=#concept-form-reset title=concept-form-reset>reset</a> the <a href=#form-owner>form owner</a>;
otherwise, it is to do nothing.<p><strong>Constraint validation:</strong> The element is
<a href=#barred-from-constraint-validation>barred from constraint validation</a>.<p>The <code title=dom-input-value><a href=#dom-input-value>value</a></code> DOM attribute
@@ -20662,7 +20663,7 @@
default behavior. If the element has a <code title=attr-input-value><a href=#attr-input-value>value</a></code> attribute, the button's label
must be the value of that attribute; otherwise, it must be the empty
string.<p>If the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>,
- the user should allow the user to activate the element. The
+ the user agent should allow the user to activate the element. The
element's <a href=#activation-behavior>activation behavior</a> is to do nothing.<p><strong>Constraint validation:</strong> The element is
<a href=#barred-from-constraint-validation>barred from constraint validation</a>.<p>The <code title=dom-input-value><a href=#dom-input-value>value</a></code> DOM attribute
applies to this element and is in mode <a href=#dom-input-value-default title=dom-input-value-default>default</a>.<p>The following content attributes must not be specified and do not
@@ -20709,12 +20710,12 @@
state indicates that the control's input data is either
particularily sensitive (for example the activation code for a
nuclear weapon) or is a value that will never be reused (for example
- a one-time-key for a bank login) and the user should therefore
+ a one-time-key for a bank login) and the user will therefore have to
explicitly enter the data each time, instead of being able to rely
on the UA to prefill the value for him.<p>Conversely, the <a href=#attr-input-autocomplete-on-state title=attr-input-autocomplete-on-state>on</a> state indicates
- that the value is not particularily sensitive and the user should
- expect to be able to rely on his UA to remember values he has
- entered for that control.<p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute is in
+ that the value is not particularily sensitive and the user can
+ expect to be able to rely on his user agent to remember values he
+ has entered for that control.<p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute is in
the <a href=#attr-input-autocomplete-on-state title=attr-input-autocomplete-on-state>on</a> state,
the user agent may store the value entered by the user so that if
the user returns to the page, the UA can prefill the form. When an
@@ -21322,7 +21323,7 @@
readonly attribute long <span title=dom-option-index>index</span>;
};</pre>
</dd>
- </dl><p class=XXX>...<p class=XXX>... <dfn id=concept-option-selected title=concept-option-selected>selected</dfn>/<dfn id=concept-option-selectedness title=concept-option-selectedness>selectedness</dfn><p class=XXX>... <dfn id=concept-option-value title=concept-option-value>value</dfn><p class=XXX>... <dfn id=concept-option-disabled title=concept-option-disabled>disabled</dfn><p class=XXX>... <dfn id=concept-option-index title=concept-option-index>index</dfn><p class=XXX>
+ </dl><p class=XXX>...<p class=XXX>... <dfn id=concept-option-selectedness title=concept-option-selectedness>selectedness</dfn><p class=XXX>... <dfn id=concept-option-value title=concept-option-value>value</dfn><p class=XXX>... <dfn id=concept-option-disabled title=concept-option-disabled>disabled</dfn><p class=XXX>... <dfn id=concept-option-index title=concept-option-index>index</dfn><p class=XXX>
<dfn id=dom-option title=dom-option><code>Option()</code></dfn>
<dfn id=dom-option-n title=dom-option-n><code>Option(<var title="">name</var>)</code></dfn>
<dfn id=dom-option-nv title=dom-option-nv><code>Option(<var title="">name</var>, <var title="">value</var>)</code></dfn>
@@ -21729,8 +21730,9 @@
<li><p>If the <var title="">field</var> element is a
<code><a href=#the-select-element>select</a></code> element, then for each <code><a href=#the-option-element>option</a></code>
- element in the <code><a href=#the-select-element>select</a></code> element that is <a href=#concept-option-selected title=concept-option-selected>selected</a>, append an entry
- in the <var title="">form data set</var> with the <var title="">name</var> as the name and the <a href=#concept-option-value title=concept-option-value>value</a> of the
+ element in the <code><a href=#the-select-element>select</a></code> element whose <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> is true,
+ append an entry in the <var title="">form data set</var> with the
+ <var title="">name</var> as the name and the <a href=#concept-option-value title=concept-option-value>value</a> of the
<code><a href=#the-option-element>option</a></code> element as the value.</li>
<li>
@@ -22126,13 +22128,12 @@
content attribute is a <a href=#boolean-attribute>boolean attribute</a>. If present,
it indicates that the details should be shown to the user. If the
attribute is absent, the details should not be shown.<p>If the attribute is removed, then the details should be
- hidden. If the attribute is added, the details should be shown.<p>The user should be able to request that the details be shown or
- hidden. To honor a request for the details to be shown, the user
- agent must set the <code title=attr-details-open><a href=#attr-details-open>open</a></code>
- attribute on the element to the value <code title="">open</code>. To
- honour a request for the details to be hidden, the user agent must
- remove the <code title=attr-details-open><a href=#attr-details-open>open</a></code> attribute
- from the element.<p>The <dfn id=dom-details-open title=dom-details-open><code>open</code></dfn>
+ hidden. If the attribute is added, the details should be shown.<p>The user agent should allow the user to request that the details
+ be shown or hidden. To honor a request for the details to be shown,
+ the user agent must set the <code title=attr-details-open><a href=#attr-details-open>open</a></code> attribute on the element to
+ the value <code title="">open</code>. To honour a request for the
+ details to be hidden, the user agent must remove the <code title=attr-details-open><a href=#attr-details-open>open</a></code> attribute from the
+ element.<p>The <dfn id=dom-details-open title=dom-details-open><code>open</code></dfn>
attribute must <a href=#reflect>reflect</a> the <code title=attr-details-open><a href=#attr-details-open>open</a></code> content attribute.<p class=XXX>Rendering will be described in the Rendering
section in due course. Basically CSS :open and :closed match the
element, it's a block-level element by default, and when it matches
@@ -23082,10 +23083,10 @@
relative to a particular column</dt>
<dd>Check whether the <code title=datagrid-column-class-sortable><a href=#datagrid-column-class-sortable>sortable</a></code> class
- applies to the column. If it does, then the user should be able to
- ask the UA to display the data sorted by that column; if it does
- not, then the user agent must not allow the user to ask for the
- data to be sorted by that column.</dd>
+ applies to the column. If it does, then the user agent should offer
+ the user the option to have the data displayed sorted by that
+ column; if it does not, then the user agent must not allow the user
+ to ask for the data to be sorted by that column.</dd>
<dt>To establish if a column is a sorted column</dt>
@@ -23422,22 +23423,22 @@
itself when the data provider signals changes to the data, though.
Obviously, conformance requirements stating that
<code><a href=#datagrid>datagrid</a></code> elements must react to users in particular
- ways do not apply when one is disabled.<p>If <a href=#rowType1>a row is openable</a>, then the user
- should be able to toggle its open/closed state. When a row's
- open/closed state changes, the user agent must update the rendering
- to match the new state.<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" behavior of a cell, then the <code><a href=#datagrid>datagrid</a></code> must
- invoke the data provider's <code title=dom-provider-cycleCell><a href=#dom-provider-cyclecell>cycleCell()</a></code> method, with a
+ ways do not apply when one is disabled.<p>If <a href=#rowType1>a row is openable</a>, then the user agent
+ should offer to the user the option of toggling the row's
+ open/closed state. When a row's open/closed state changes, the user
+ agent must update the rendering to match the new state.<p>If a cell is a cell whose value <a href=#cellType1>can be
+ cycled between multiple states</a>, then the user agent should allow
+ the user to activate the cell to cycle its value. When the user
+ activates this "cycling" behavior of a cell, then the
+ <code><a href=#datagrid>datagrid</a></code> must invoke the data provider's <code title=dom-provider-cycleCell><a href=#dom-provider-cyclecell>cycleCell()</a></code> method, with a
<code><a href=#rowspecification>RowSpecification</a></code> object representing the cell's row as
the first argument and the cell's column index as the second. The
- <code><a href=#datagrid>datagrid</a></code> must then act as if the <code><a href=#datagrid>datagrid</a></code>'s
- <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
+ <code><a href=#datagrid>datagrid</a></code> must then act as if the
+ <code><a href=#datagrid>datagrid</a></code>'s <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
method had been invoked with those same arguments.<p>When a cell <a href=#cellType2>has a checkbox</a>, the user
- must be able to set the checkbox's state. When the user changes the
- state of a checkbox in such a cell, the <code><a href=#datagrid>datagrid</a></code> must
- invoke the data provider's <code title=dom-provider-setCellCheckedState><a href=#dom-provider-setcellcheckedstate>setCellCheckedState()</a></code>
+ agent should allow the user to set the checkbox's state. When the
+ user changes the state of a checkbox in such a cell, the
+ <code><a href=#datagrid>datagrid</a></code> must invoke the data provider's <code title=dom-provider-setCellCheckedState><a href=#dom-provider-setcellcheckedstate>setCellCheckedState()</a></code>
method, with a <code><a href=#rowspecification>RowSpecification</a></code> object representing the
cell's row as the first argument, the cell's column index as the
second, and the checkbox's new state as the third. The state should
@@ -23446,13 +23447,13 @@
indeterminate (which must be possible only if the cell has the <code title=datagrid-cell-class-indeterminate><a href=#datagrid-cell-class-indeterminate>indeterminate</a></code> class
set). The <code><a href=#datagrid>datagrid</a></code> must then act as if the
<code><a href=#datagrid>datagrid</a></code>'s <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
- method had been invoked, specifying the same cell.<p>If a cell <a href=#cellType2>is editable</a>, the user must be
- able to edit the data for that cell, and doing so must cause the
- user agent to invoke the <code title=dom-provider-editCell><a href=#dom-provider-editcell>editCell()</a></code> method of the data
+ method had been invoked, specifying the same cell.<p>If a cell <a href=#cellType2>is editable</a>, the user agent
+ should allow the user to edit the data for that cell, and doing so
+ must cause the user agent to invoke the <code title=dom-provider-editCell><a href=#dom-provider-editcell>editCell()</a></code> method of the data
provider with three arguments: a <code><a href=#rowspecification>RowSpecification</a></code>
object representing the cell's row, the cell's column's index, and
- the new text entered by the user. The user agent must then act as if the
- <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
+ the new text entered by the user. The user agent must then act as if
+ the <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
method had been invoked, with the same row and column specified.</p><!-- XXXPA <p class="XXX">define actions (performAction(), etc)</p> --><h5 id=the-selection><span class=secno>4.11.2.8 </span>The selection</h5><p><em>This section only applies to interactive user agents. For
other user agents, the <code title=dom-datagrid-selection><a href=#dom-datagrid-selection>selection</a></code> attribute must
return null.</em><pre class=idl>interface <dfn id=datagridselection>DataGridSelection</dfn> {
@@ -23506,10 +23507,11 @@
method must mark all the rows in the data grid to be marked as not
selected. After a call to <code title=dom-DataGridSelection-clear><a href=#dom-datagridselection-clear>clear()</a></code>, the <code title=dom-DataGridSelection-length><a href=#dom-datagridselection-length>length</a></code> attribute will
return zero.<p>If the <code><a href=#datagrid>datagrid</a></code> element has a <dfn id=attr-datagrid-multiple title=attr-datagrid-multiple><code>multiple</code></dfn>
- attribute, then the user must be able to select any number of rows
- (zero or more). If the attribute is not present, then the user must
- not be able to select more than a single row at a time, and
- selecting another one must unselect all the other rows.<p class=note>This only applies to the user. Scripts can select
+ attribute, then the user agent should allow the user to select any
+ number of rows (zero or more). If the attribute is not present, then
+ the user agent must not allow the user to select more than a single
+ row at a time, and selecting another one must unselect all the other
+ rows.<p class=note>This only applies to the user. Scripts can select
multiple rows even when the <code title=attr-datagrid-multiple><a href=#attr-datagrid-multiple>multiple</a></code> attribute is
absent.<p>Whenever the selection of a <code><a href=#datagrid>datagrid</a></code> changes,
whether due to the user interacting with the element, or as a result
@@ -23541,8 +23543,9 @@
with index zero, and the "last column" is always the column with the
index one less than the value returned by the <code title=dom-provider-getcolumnCount><a href=#dom-provider-getcolumncount>getColumnCount()</a></code> method
of the data provider.<p>If <a href=#columnType2>a column is sortable</a>, then the user
- must be able to invoke it to sort the data. When the user does so,
- then the <code><a href=#datagrid>datagrid</a></code> must invoke the data provider's <code title=dom-provider-toggleColumnSortState><a href=#dom-provider-togglecolumnsortstate>toggleColumnSortState()</a></code>
+ agent should allow the user to request that the data be sorted using
+ that column. When the user does so, then the <code><a href=#datagrid>datagrid</a></code>
+ must invoke the data provider's <code title=dom-provider-toggleColumnSortState><a href=#dom-provider-togglecolumnsortstate>toggleColumnSortState()</a></code>
method, with the column's index as the only argument. The
<code><a href=#datagrid>datagrid</a></code> must <em>then</em> act as if the
<code><a href=#datagrid>datagrid</a></code>'s <code title=dom-datagrid-updateEverything><a href=#dom-datagrid-updateeverything>updateEverything()</a></code>
@@ -23820,7 +23823,7 @@
interact with.<p>If a <code><a href=#menus>menu</a></code> element's <code title=attr-menu-type><a href=#attr-menu-type>type</a></code> attribute is in the <a href=#list-state title="list state">list</a> state, then the element either
represents an unordered list of items (each represented by an
<code><a href=#the-li-element>li</a></code> element), each of which represents a command that
- the user may perform or activate, or, if the element has no
+ the user can perform or activate, or, if the element has no
<code><a href=#the-li-element>li</a></code> element children, <a href=#flow-content-0>flow content</a>
describing available commands.<p>The <dfn id=attr-menu-label title=attr-menu-label><code>label</code></dfn>
attribute gives the label of the menu. It is used by user agents to
@@ -28668,8 +28671,8 @@
the user didn't cancel the request, the user agent must cache
the resource in all the application caches that have a <a href=#concept-appcache-matches-oppcache title=concept-appcache-matches-oppcache>matching opportunistic
caching namespace</a>, categorized as <a href=#concept-appcache-oppcache title=concept-appcache-oppcache>opportunistically cached
- entries</a>. Meanwhile, the user must continue along these
- steps.</p>
+ entries</a>. Meanwhile, the user agent must continue along
+ these steps.</p>
</dd>
@@ -30912,11 +30915,12 @@
this method for usability reasons.<h3 id=selection><span class=secno>6.6 </span>The text selection APIs</h3><p>Every <a href=#browsing-context>browsing context</a> has <dfn id=the-selection-0 title="the
selection">a selection</dfn>. The selection can be empty, and the
selection can have more than one range (a disjointed selection). The
- user should be able to change the selection. User agents are not
- required to let the user select more than one range, and may
- collapse multiple ranges in the selection to a single range when the
- user interacts with the selection. (But, of course, the user agent
- may let the user create selections with multiple ranges.)<p>This one selection must be shared by all the content of the
+ user agent should allow the user to change the selection. User
+ agents are not required to let the user select more than one range,
+ and may collapse multiple ranges in the selection to a single range
+ when the user interacts with the selection. (But, of course, the
+ user agent may let the user create selections with multiple
+ ranges.)<p>This one selection must be shared by all the content of the
browsing context (though not by nested <a href=#browsing-context title="browsing
context">browsing contexts</a>), including any editing hosts in
the document. (Editing hosts that are not inside a document cannot
@@ -32232,8 +32236,8 @@
the UA). If the user agent creates an <code><a href=#the-a-element>a</a></code> element or
modifies an existing <code><a href=#the-a-element>a</a></code> element, then if the <var title="">showUI</var> argument is present and has the value false,
then the value of the <var title="">value</var> argument must be
- used as the <a href=#url>URL</a> of the link. Otherwise, the user
- should be prompted for the URL of the link.</dd>
+ used as the <a href=#url>URL</a> of the link. Otherwise, the user agent
+ should prompt the user for the URL of the link.</dd>
<dd><strong>Enabled When:</strong> The document is <a href=#ready-for-editing-host-commands>ready for
editing host commands</a>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -32305,7 +32309,7 @@
modifies an existing <code><a href=#the-img-element>img</a></code> element, then if the <var title="">showUI</var> argument is present and has the value false,
then the value of the <var title="">value</var> argument must be
used as the <a href=#url>URL</a> of the image. Otherwise, the user
- should be prompted for the URL of the image.</dd>
+ agent should prompt the user for the URL of the image.</dd>
<dd><strong>Enabled When:</strong> The document is <a href=#ready-for-editing-host-commands>ready for
editing host commands</a>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
Received on Tuesday, 7 October 2008 21:29:23 UTC