- From: poot <cvsmail@w3.org>
- Date: Tue, 01 Mar 2011 18:20:40 -0500
- To: public-html-diffs@w3.org
hixie: Make an explicit conformance class for people who implement the
rendering section. (whatwg r5923)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4763&r2=1.4764&f=h
http://html5.org/tools/web-apps-tracker?from=5922&to=5923
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4763
retrieving revision 1.4764
diff -u -d -r1.4763 -r1.4764
--- Overview.html 1 Mar 2011 22:57:26 -0000 1.4763
+++ Overview.html 1 Mar 2011 23:18:29 -0000 1.4764
@@ -2628,6 +2628,21 @@
</dd>
+ <dt id="renderingUA">Visual user agents that support the suggested default rendering</dt>
+
+ <dd>
+
+ <p>User agents, whether interactive or not, may be designated
+ (possibly as a user option) as supporting the suggested default
+ rendering defined by this specification.</p>
+
+ <p>User agents that are designated as supporting the suggested
+ default rendering must implement the rules in <a href="#rendering">the rendering section</a> that that section
+ defines as the behavior that user agents are <em>expected</em> to
+ implement.</p>
+
+ </dd>
+
<dt><dfn id="non-scripted">User agents with no scripting support</dfn></dt>
<dd>
@@ -2647,6 +2662,7 @@
</dd>
+
<dt>Conformance checkers</dt>
<dd id="conformance-checkers">
@@ -2703,6 +2719,7 @@
</div>
</dd>
+
<dt>Data mining tools</dt>
<dd id="data-mining">
@@ -2718,6 +2735,7 @@
</dd>
+
<dt id="editors">Authoring tools and markup generators</dt>
<dd>
@@ -63403,7 +63421,11 @@
by the documents' authors. So as to avoid confusion regarding the
normativity of this section, RFC2119 terms have not been used.
Instead, the term "expected" is used to indicate behavior that will
- lead to this experience.</i></p>
+ lead to this experience. For the purposes of conformance for user
+ agents designated as <a href="#renderingUA">supporting the suggested
+ default rendering</a>, the term "expected" in this section has the
+ same conformance implications as the RFC2119-defined term
+ "must".</i></p>
<h3 id="introduction-7"><span class="secno">10.1 </span>Introduction</h3>
Received on Tuesday, 1 March 2011 23:20:42 UTC