[html5] r2294 - [e] (0) The user is not a conformance class... (credit: sp)
whatwg at whatwg.org
whatwg at whatwg.org
Tue Oct 7 14:28:40 PDT 2008
Author: ianh
Date: 2008-10-07 14:28:39 -0700 (Tue, 07 Oct 2008)
New Revision: 2294
Modified:
index
source
Log:
[e] (0) The user is not a conformance class... (credit: sp)
Modified: index
===================================================================
--- index 2008-10-07 21:21:13 UTC (rev 2293)
+++ index 2008-10-07 21:28:39 UTC (rev 2294)
@@ -24023,7 +24023,7 @@
single e-mail address given in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>.</p>
<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
@@ -24091,8 +24091,9 @@
single <a href=#url>URL</a> given in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>.</p>
<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
@@ -24215,7 +24216,7 @@
whatever timezone is appropriate for the user.</p>
<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
@@ -24327,7 +24328,7 @@
string representing a specific <a href=#concept-date title=concept-date>date</a>.</p>
<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>,
@@ -24441,7 +24442,7 @@
string representing a specific <a href=#concept-month title=concept-month>month</a>.</p>
<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>,
@@ -24555,7 +24556,7 @@
string representing a specific <a href=#concept-week title=concept-week>week</a>.</p>
<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>,
@@ -24669,7 +24670,7 @@
string representing a specific <a href=#concept-time title=concept-time>time</a>.</p>
<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>,
@@ -24778,7 +24779,7 @@
date and time</a>, with no time zone information.</p>
<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
@@ -24877,12 +24878,12 @@
string representing a number.</p>
<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>
@@ -24978,12 +24979,12 @@
value to the empty string.</p>
<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>
@@ -25268,10 +25269,10 @@
contents of the file).</p>
<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>
+ 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>
<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
@@ -25366,7 +25367,7 @@
implementation-defined string that means "Submit" or some such.</p>
<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 user agent should allow the user to activate the element.</p>
<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
@@ -25495,8 +25496,8 @@
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>
@@ -25505,9 +25506,9 @@
<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>
@@ -25584,7 +25585,7 @@
implementation-defined string that means "Reset" or some such.</p>
<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 user agent should allow the user to activate the element.</p>
<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>;
@@ -25641,7 +25642,7 @@
string.</p>
<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>
<p><strong>Constraint validation:</strong> The element is
@@ -25719,14 +25720,14 @@
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>
<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>
+ 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>
<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,
@@ -26567,7 +26568,7 @@
</dd>
</dl><p class=XXX>...</p>
- <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>
+ <p class=XXX>... <dfn id=concept-option-selectedness title=concept-option-selectedness>selectedness</dfn></p>
<p class=XXX>... <dfn id=concept-option-value title=concept-option-value>value</dfn></p>
@@ -27164,8 +27165,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>
@@ -27601,13 +27603,12 @@
<p>If the attribute is removed, then the details should be
hidden. If the attribute is added, the details should be shown.</p>
- <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>
+ <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>
<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>
@@ -28653,10 +28654,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>
@@ -29035,26 +29036,26 @@
<code><a href=#datagrid>datagrid</a></code> elements must react to users in particular
ways do not apply when one is disabled.</p>
- <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>
+ <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>
<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
+ 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>
<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
@@ -29065,13 +29066,13 @@
<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>
- <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
+ <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> -->
@@ -29155,10 +29156,11 @@
return zero.</p>
<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>
+ 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>
<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
@@ -29211,8 +29213,9 @@
of the data provider.</p>
<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>
@@ -29594,7 +29597,7 @@
<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>
@@ -35654,8 +35657,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>
@@ -38833,11 +38836,12 @@
<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>
+ 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>
<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
@@ -40613,8 +40617,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>
@@ -40686,7 +40690,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>
Modified: source
===================================================================
--- source 2008-10-07 21:21:13 UTC (rev 2293)
+++ source 2008-10-07 21:28:39 UTC (rev 2294)
@@ -26709,7 +26709,7 @@
title="concept-fe-value">value</span>.</p>
<p>If the element is <i title="concept-input-mutable">mutable</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 <span title="concept-fe-value">value</span>. User
agents may allow the user to set the <span
title="concept-fe-value">value</span> to a string that is not an
@@ -26786,9 +26786,9 @@
title="concept-fe-value">value</span>.</p>
<p>If the is <i title="concept-input-mutable">mutable</i>, the user
- should allow the user to change the URL represented by its <span
- title="concept-fe-value">value</span>. User agents may allow the
- user to set the <span title="concept-fe-value">value</span> to a
+ agent should allow the user to change the URL represented by its
+ <span title="concept-fe-value">value</span>. User agents may allow
+ the user to set the <span title="concept-fe-value">value</span> to a
string that is not a <span>valid URL</span>. User agents should
allow the user to set the <span
title="concept-fe-value">value</span> to the empty string. User
@@ -26922,7 +26922,7 @@
whatever timezone is appropriate for the user.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-datetime">UTC date and time</span> represented by its
<span title="concept-fe-value">value</span>, as obtained by <span
title="parse a UTC date and time string">parsing a UTC date and
@@ -27057,7 +27057,7 @@
title="concept-date">date</span>.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-date">date</span> represented by its <span
title="concept-fe-value">value</span>, as obtained by <span
title="parse a date string">parsing a date</span> from it. User
@@ -27189,7 +27189,7 @@
title="concept-month">month</span>.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-month">month</span> represented by its <span
title="concept-fe-value">value</span>, as obtained by <span
title="parse a month string">parsing a month</span> from it. User
@@ -27323,7 +27323,7 @@
title="concept-week">week</span>.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-week">week</span> represented by its <span
title="concept-fe-value">value</span>, as obtained by <span
title="parse a week string">parsing a week</span> from it. User
@@ -27456,7 +27456,7 @@
title="concept-time">time</span>.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-time">time</span> represented by its <span
title="concept-fe-value">value</span>, as obtained by <span
title="parse a time string">parsing a time</span> from it. User
@@ -27584,7 +27584,7 @@
date and time</span>, with no time zone information.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the <span
+ the user agent should allow the user to change the <span
title="concept-datetime-local">date and time</span> represented by
its <span title="concept-fe-value">value</span>, as obtained by
<span title="parse a local date and time string">parsing a date and
@@ -27698,12 +27698,12 @@
string representing a number.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the number represented by
- its <span title="concept-fe-value">value</span>, as obtained from
- applying the <span>rules for parsing floating point number
- values</span> to it. User agents must not allow the user to set the
- <span title="concept-fe-value">value</span> to a string that is not
- a <span>valid floating point number</span>. If the user agent
+ the user agent should allow the user to change the number
+ represented by its <span title="concept-fe-value">value</span>, as
+ obtained from applying the <span>rules for parsing floating point
+ number values</span> to it. User agents must not allow the user to
+ set the <span title="concept-fe-value">value</span> to a string that
+ is not a <span>valid floating point number</span>. If the user agent
provides a user interface for selecting a number, then the <span
title="concept-fe-value">value</span> must be set to a <span>valid
floating point number</span> representing the user's selection. User
@@ -27809,12 +27809,12 @@
value to the empty string.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to change the number represented by
- its <span title="concept-fe-value">value</span>, as obtained from
- applying the <span>rules for parsing floating point number
- values</span> to it. User agents must not allow the user to set the
- <span title="concept-fe-value">value</span> to a string that is not
- a <span>valid floating point number</span>. If the user agent
+ the user agent should allow the user to change the number
+ represented by its <span title="concept-fe-value">value</span>, as
+ obtained from applying the <span>rules for parsing floating point
+ number values</span> to it. User agents must not allow the user to
+ set the <span title="concept-fe-value">value</span> to a string that
+ is not a <span>valid floating point number</span>. If the user agent
provides a user interface for selecting a number, then the <span
title="concept-fe-value">value</span> must be set to a <span>valid
floating point number</span> representing the user's selection. User
@@ -28146,10 +28146,10 @@
contents of the file).</p>
<p>If the element is <i title="concept-input-mutable">mutable</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>
+ 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>
<p><strong>Constraint validation:</strong> If the element is <i
title="concept-input-required">required</i> and the list of <span
@@ -28260,7 +28260,7 @@
implementation-defined string that means "Submit" or some such.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to activate the element.</p>
+ the user agent should allow the user to activate the element.</p>
<p>The element's <span>activation behavior</span>, if the element
has a <span>form owner</span>, is to <span
@@ -28426,8 +28426,8 @@
title="concept-input-type-image-coordinate">coordinate</span> from
the image specified by the <code title="attr-input-src">src</code>
attribute; if the element is <i
- title="concept-input-mutable">mutable</i>, the user should allow the
- user to select this <span
+ title="concept-input-mutable">mutable</i>, the user agent should
+ allow the user to select this <span
title="concept-input-type-image-coordinate">coordinate</span>. The
<span>activation behavior</span> in this case consists of taking the
user's selected <span
@@ -28440,9 +28440,9 @@
<p>Otherwise, the element represents a submit button whose label is
given by the value of the <code title="attr-input-alt">alt</code>
attribute; if the element is <i
- title="concept-input-mutable">mutable</i>, the user should allow the
- user to activate the button. The <span>activation behavior</span> in
- this case consists of setting the <span
+ title="concept-input-mutable">mutable</i>, the user agent should
+ allow the user to activate the button. The <span>activation
+ behavior</span> in this case consists of setting the <span
title="concept-input-type-image-coordinate">selected
coordinate</span> to (0,0), and then, if the element has a
<span>form owner</span>, <span
@@ -28533,7 +28533,7 @@
implementation-defined string that means "Reset" or some such.</p>
<p>If the element is <i title="concept-input-mutable">mutable</i>,
- the user should allow the user to activate the element.</p>
+ the user agent should allow the user to activate the element.</p>
<p>The element's <span>activation behavior</span>, if the element
has a <span>form owner</span>, is to <span
@@ -28597,7 +28597,7 @@
string.</p>
<p>If the element is <i title="concept-input-mutable">mutable</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 <span>activation behavior</span> is to do nothing.</p>
<p><strong>Constraint validation:</strong> The element is
@@ -28682,15 +28682,15 @@
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>
<p>Conversely, the <span
title="attr-input-autocomplete-on-state">on</span> 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>
+ 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>
<p>When an <code>input</code> element's <code
title="attr-input-autocomplete">autocomplete</code> attribute is in
@@ -29752,7 +29752,7 @@
<p class="XXX">...</p>
- <p class="XXX">... <dfn title="concept-option-selected">selected</dfn>/<dfn title="concept-option-selectedness">selectedness</dfn></p>
+ <p class="XXX">... <dfn title="concept-option-selectedness">selectedness</dfn></p>
<p class="XXX">... <dfn title="concept-option-value">value</dfn></p>
@@ -30461,10 +30461,10 @@
<li><p>If the <var title="">field</var> element is a
<code>select</code> element, then for each <code>option</code>
- element in the <code>select</code> element that is <span
- title="concept-option-selected">selected</span>, append an entry
- in the <var title="">form data set</var> with the <var
- title="">name</var> as the name and the <span
+ element in the <code>select</code> element whose <span
+ title="concept-option-selectedness">selectedness</span> is true,
+ append an entry in the <var title="">form data set</var> with the
+ <var title="">name</var> as the name and the <span
title="concept-option-value">value</span> of the
<code>option</code> element as the value.</p></li>
@@ -31022,13 +31022,14 @@
<p>If the attribute is removed, then the details should be
hidden. If the attribute is added, the details should be shown.</p>
- <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">open</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">open</code> attribute
- from the element.</p>
+ <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">open</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">open</code> attribute from the
+ element.</p>
<p>The <dfn title="dom-details-open"><code>open</code></dfn>
attribute must <span>reflect</span> the <code
@@ -32332,10 +32333,10 @@
<dd>Check whether the <code
title="datagrid-column-class-sortable">sortable</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>
@@ -32792,28 +32793,28 @@
<code>datagrid</code> elements must react to users in particular
ways do not apply when one is disabled.</p>
- <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>
+ <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>
<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>datagrid</code> must
- invoke the data provider's <code
+ 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>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
the first argument and the cell's column index as the second. The
- <code>datagrid</code> must then act as if the <code>datagrid</code>'s
- <code
+ <code>datagrid</code> must then act as if the
+ <code>datagrid</code>'s <code
title="dom-datagrid-updateCellChanged">updateCellChanged()</code>
method had been invoked with those same arguments.</p>
<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>datagrid</code> must
- invoke the data provider's <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>datagrid</code> must invoke the data provider's <code
title="dom-provider-setCellCheckedState">setCellCheckedState()</code>
method, with a <code>RowSpecification</code> object representing the
cell's row as the first argument, the cell's column index as the
@@ -32827,14 +32828,14 @@
title="dom-datagrid-updateCellChanged">updateCellChanged()</code>
method had been invoked, specifying the same cell.</p>
- <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
+ <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">editCell()</code> method of the data
provider with three arguments: a <code>RowSpecification</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
+ the new text entered by the user. The user agent must then act as if
+ the <code
title="dom-datagrid-updateCellChanged">updateCellChanged()</code>
method had been invoked, with the same row and column specified.</p>
@@ -32935,10 +32936,11 @@
<p>If the <code>datagrid</code> element has a <dfn
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>
+ 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>
<p class="note">This only applies to the user. Scripts can select
multiple rows even when the <code
@@ -32997,8 +32999,9 @@
of the data provider.</p>
<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>datagrid</code> must invoke the data provider's <code
+ agent should allow the user to request that the data be sorted using
+ that column. When the user does so, then the <code>datagrid</code>
+ must invoke the data provider's <code
title="dom-provider-toggleColumnSortState">toggleColumnSortState()</code>
method, with the column's index as the only argument. The
<code>datagrid</code> must <em>then</em> act as if the
@@ -33441,7 +33444,7 @@
title="list state">list</span> state, then the element either
represents an unordered list of items (each represented by an
<code>li</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>li</code> element children, <span>flow content</span>
describing available commands.</p>
@@ -40476,8 +40479,8 @@
title="concept-appcache-matches-oppcache">matching opportunistic
caching namespace</span>, categorized as <span
title="concept-appcache-oppcache">opportunistically cached
- entries</span>. Meanwhile, the user must continue along these
- steps.</p>
+ entries</span>. Meanwhile, the user agent must continue along
+ these steps.</p>
</dd>
@@ -44093,11 +44096,12 @@
<p>Every <span>browsing context</span> has <dfn 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>
+ 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>
<p>This one selection must be shared by all the content of the
browsing context (though not by nested <span title="browsing
@@ -46225,8 +46229,8 @@
modifies an existing <code>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 <span>URL</span> of the link. Otherwise, the user
- should be prompted for the URL of the link.</dd>
+ used as the <span>URL</span> 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 <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -46303,7 +46307,7 @@
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 <span>URL</span> 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 <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
More information about the Commit-Watchers
mailing list