[html5] r1586 - /
whatwg at whatwg.org
whatwg at whatwg.org
Fri May 9 01:06:53 PDT 2008
Author: ianh
Date: 2008-05-09 01:06:52 -0700 (Fri, 09 May 2008)
New Revision: 1586
Modified:
index
source
Log:
[c] (0) ...and 'should only' goes byebye also.
Modified: index
===================================================================
--- index 2008-05-09 08:03:48 UTC (rev 1585)
+++ index 2008-05-09 08:06:52 UTC (rev 1586)
@@ -2176,8 +2176,9 @@
informed choices regarding which HTML elements and attributes are most
appropriate.</p>
- <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should only use
- elements they know are appropriate. This might in certain extreme cases
+ <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should use
+ elements they know are appropriate, and should not use elements that
+ they do not know to be appropriate. This might in certain extreme cases
mean limiting the use of flow elements to just a few elements, like
<code><a href="#div">div</a></code>, <code><a href="#b">b</a></code>,
<code><a href="#i">i</a></code>, and <code><a
@@ -12580,9 +12581,9 @@
presentation's sake. For example, it would be inappropriate for the
<code><a href="#sub">sub</a></code> and <code><a
href="#sup">sup</a></code> elements to be used in the name of the LaTeX
- document preparation system. In general, authors should only use these
- elements if the <em>absence</em> of those elements would change the
- meaning of the content.
+ document preparation system. In general, authors should use these elements
+ only if the <em>absence</em> of those elements would change the meaning of
+ the content.
<p>When the <code><a href="#sub">sub</a></code> element is used inside a
<code><a href="#var">var</a></code> element, it represents the subscript
@@ -25027,7 +25028,7 @@
change to the selection, and must therefore not fire the <code
title=event-select><a href="#select">select</a></code> event.
- <p>These update methods should only be called by the data provider, or code
+ <p>These update methods should be called only by the data provider, or code
acting on behalf of the data provider. In particular, calling the <code
title=dom-datagrid-updateRowsInserted><a
href="#updaterowsinserted">updateRowsInserted()</a></code> and <code
@@ -33114,7 +33115,7 @@
<p>User agents must have a set of local storage areas, one for each <a
href="#origin0">origin</a>.
- <p>User agents should only expire data from the local storage areas for
+ <p>User agents should expire data from the local storage areas only for
security reasons or when requested to do so by the user. User agents
should always avoid deleting data while a script that could access that
data is running. Data stored in local storage areas should be considered
@@ -35865,13 +35866,13 @@
<p>In response to a request from a user to mark text up in italics, user
agents should use the <code><a href="#i">i</a></code> element to
represent the semantic. The <code><a href="#em">em</a></code> element
- should only be used if the user agent is sure that the user means to
+ should be used only if the user agent is sure that the user means to
indicate stress emphasis.</p>
<p>In response to a request from a user to mark text up in bold, user
agents should use the <code><a href="#b">b</a></code> element to
represent the semantic. The <code><a href="#strong">strong</a></code>
- element should only be used if the user agent is sure that the user
+ element should be used only if the user agent is sure that the user
means to indicate importance.</p>
<p>The exact behavior is UA-dependent, but user agents must not, in
@@ -51204,7 +51205,7 @@
context menus and menus for application menu bars, and to only use
styles for in-page menus.</p>
- <p>If user agents support styling of menus, they should only support
+ <p>If user agents support styling of menus, they should support only
the '<code>background</code>', '<code>color</code>',
'<code>border</code>', '<code>padding</code>' and
'<code>font</code>' properties on menus and menu items. (This list
Modified: source
===================================================================
--- source 2008-05-09 08:03:48 UTC (rev 1585)
+++ source 2008-05-09 08:06:52 UTC (rev 1586)
@@ -427,8 +427,9 @@
make informed choices regarding which HTML elements and attributes
are most appropriate.</p>
- <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should
- only use elements they know are appropriate. This might in certain
+ <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should use
+ elements they know are appropriate, and should not use elements
+ that they do not know to be appropriate. This might in certain
extreme cases mean limiting the use of flow elements to just a few
elements, like <code>div</code>, <code>b</code>, <code>i</code>,
and <code>span</code> and making liberal use of the <code
@@ -10647,7 +10648,7 @@
presentation for presentation's sake. For example, it would be
inappropriate for the <code>sub</code> and <code>sup</code> elements
to be used in the name of the LaTeX document preparation system. In
- general, authors should only use these elements if the
+ general, authors should use these elements only if the
<em>absence</em> of those elements would change the meaning of the
content.</p>
@@ -22809,7 +22810,7 @@
selection, and must therefore not fire the <code
title="event-select">select</code> event.</p>
- <p>These update methods should only be called by the data provider,
+ <p>These update methods should be called only by the data provider,
or code acting on behalf of the data provider. In particular,
calling the <code
title="dom-datagrid-updateRowsInserted">updateRowsInserted()</code>
@@ -30901,7 +30902,7 @@
<p>User agents must have a set of local storage areas, one for each
<span>origin</span>.</p>
- <p>User agents should only expire data from the local storage areas
+ <p>User agents should expire data from the local storage areas only
for security reasons or when requested to do so by the user. User
agents should always avoid deleting data while a script that could
access that data is running. Data stored in local storage areas
@@ -33555,13 +33556,13 @@
<p>In response to a request from a user to mark text up in italics,
user agents should use the <code>i</code> element to represent the
- semantic. The <code>em</code> element should only be used if the
+ semantic. The <code>em</code> element should be used only if the
user agent is sure that the user means to indicate stress
emphasis.</p>
<p>In response to a request from a user to mark text up in bold,
user agents should use the <code>b</code> element to represent the
- semantic. The <code>strong</code> element should only be used if
+ semantic. The <code>strong</code> element should be used only if
the user agent is sure that the user means to indicate
importance.</p>
@@ -46490,7 +46491,7 @@
context menus and menus for application menu bars, and to only use
styles for in-page menus.</p>
- <p>If user agents support styling of menus, they should only support
+ <p>If user agents support styling of menus, they should support only
the '<code>background</code>', '<code>color</code>',
'<code>border</code>', '<code>padding</code>' and
'<code>font</code>' properties on menus and menu items. (This list
More information about the Commit-Watchers
mailing list