[html5] r1513 - /
whatwg at whatwg.org
whatwg at whatwg.org
Tue Apr 29 05:43:51 PDT 2008
Author: ianh
Date: 2008-04-29 05:43:51 -0700 (Tue, 29 Apr 2008)
New Revision: 1513
Modified:
index
source
Log:
[ec] (0) Fallout from removing the WYSIWYG section.
Modified: index
===================================================================
--- index 2008-04-29 12:28:21 UTC (rev 1512)
+++ index 2008-04-29 12:43:51 UTC (rev 1513)
@@ -1959,10 +1959,9 @@
HTML.
</dl>
- <p>There are also a couple of appendices, defining <a href="#wysiwyg">shims
- for WYSIWYG editors</a>, <a href="#rendering">rendering rules</a> for Web
- browsers, and listing <a href="#no">areas that are out of scope</a> for
- this specification.
+ <p>There are also a couple of appendices, defining <a
+ href="#rendering">rendering rules</a> for Web browsers and listing <a
+ href="#no">areas that are out of scope</a> for this specification.
<h4 id=how-to><span class=secno>1.2.1 </span>How to read this specification</h4>
@@ -2169,9 +2168,13 @@
informed choices regarding which HTML elements and attributes are most
appropriate.</p>
- <p>However, WYSIWYG tools are legitimate, and this specification <span
- title="WYSIWYG editors">makes certain concessions to WYSIWYG
- editors</span>.</p>
+ <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should only use
+ elements they know are 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
+ href="#span">span</a></code> and making liberal use of the <code
+ title=attr-style><a href="#style">style</a></code> attribute.</p>
<p>All authoring tools, whether WYSIWYG or not, should make a best effort
attempt at enabling users to create well-structured, semantically rich,
@@ -7796,8 +7799,7 @@
<dd>
<p>The value must be a free-form string that identifies the software used
to generate the document. This value must not be used on hand-authored
- pages. WYSIWYG editors have <span title="WYSIWYG signature">additional
- constraints</span> on the value used with this metadata name.
+ pages.
<dt><dfn id=dns title=meta-dns>dns</dfn>
Modified: source
===================================================================
--- source 2008-04-29 12:28:21 UTC (rev 1512)
+++ source 2008-04-29 12:43:51 UTC (rev 1513)
@@ -192,8 +192,7 @@
</dl>
<p>There are also a couple of appendices, defining <a
- href="#wysiwyg">shims for WYSIWYG editors</a>, <a
- href="#rendering">rendering rules</a> for Web browsers, and listing
+ href="#rendering">rendering rules</a> for Web browsers and listing
<a href="#no">areas that are out of scope</a> for this
specification.</p>
@@ -428,9 +427,12 @@
make informed choices regarding which HTML elements and attributes
are most appropriate.</p>
- <p>However, WYSIWYG tools are legitimate, and this specification
- <span title="WYSIWYG editors">makes certain concessions to WYSIWYG
- editors</span>.</p>
+ <p>However, WYSIWYG tools are legitimate. WYSIWYG tools should
+ only use elements they know are 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
+ title="attr-style">style</code> attribute.</p>
<p>All authoring tools, whether WYSIWYG or not, should make a best
effort attempt at enabling users to create well-structured,
@@ -6194,9 +6196,7 @@
<dd><p>The value must be a free-form string that identifies the
software used to generate the document. This value must not be used
- on hand-authored pages. WYSIWYG editors have <span title="WYSIWYG
- signature">additional constraints</span> on the value used with
- this metadata name.</p></dd>
+ on hand-authored pages.</p></dd>
<dt><dfn title="meta-dns">dns</dfn></dt>
More information about the Commit-Watchers
mailing list