html5/spec Overview.html,1.2277,1.2278

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27500

Modified Files:
	Overview.html 
Log Message:
Drop in some 'Extensibility' text from WF2. (whatwg r3120)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2277
retrieving revision 1.2278
diff -u -d -r1.2277 -r1.2278
--- Overview.html	24 May 2009 01:38:09 -0000	1.2277
+++ Overview.html	24 May 2009 05:15:12 -0000	1.2278
@@ -300,7 +300,8 @@
      <li><a href="#dependencies"><span class="secno">2.2.1 </span>Dependencies</a></li>
      <li><a href="#features-defined-in-other-specifications"><span class="secno">2.2.2 </span>Features defined in other specifications</a></li>
      <li><a href="#common-conformance-requirements-for-apis-exposed-to-javascript"><span class="secno">2.2.3 </span>Common conformance requirements for APIs exposed to
-  JavaScript</a></ol></li>
+  JavaScript</a></li>
+     <li><a href="#extensibility"><span class="secno">2.2.4 </span>Extensibility</a></ol></li>
    <li><a href="#case-sensitivity-and-string-comparison"><span class="secno">2.3 </span>Case-sensitivity and string comparison</a></li>
    <li><a href="#common-microsyntaxes"><span class="secno">2.4 </span>Common microsyntaxes</a>
     <ol>
@@ -1867,6 +1868,43 @@
   is defined for that method in its IDL definition, the excess
   arguments must be ignored.</p>
 
+  </div><div class="impl">
+
+  <h4 id="extensibility"><span class="secno">2.2.4 </span>Extensibility</h4>
+
+  <p>Vendor-specific proprietary extensions to this specification are
+  strongly discouraged. Documents must not use such extensions, as
+  doing so reduces interoperability and fragments the user base,
+  allowing only users of specific user agents to access the content in
+  question.</p>
+
+  <p>If markup extensions are needed, they should be done using XML,
+  with elements or attributes from custom namespaces. If DOM
+  extensions are needed, the members should be prefixed by
+  vendor-specific strings to prevent clashes with future versions of
+  this specification. Extensions must be defined so that the use of
+  extensions does not contradict nor cause the non-conformance of
+  functionality defined in the specification.</p> <!-- thanks to QA
+  Framework -->
+
+  <div class="example">
+
+   <p>For example, while strongly discouraged to do so, an
+   implementation "Foo Browser" could add a new DOM attribute "<code title="">fooTypeTime</code>" to a control's DOM interface that
+   returned the time it took the user to select the current value of a
+   control (say). On the other hand, defining a new control that
+   appears in a form's <code title="dom-form-elements"><a href="#dom-form-elements">elements</a></code>
+   array would be in violation of the above requirement, as it would
+   violate the definition of <code title="dom-form-elements"><a href="#dom-form-elements">elements</a></code> given in this
+   specification.</p>
+
+  </div>
+
+  <p>User agents must treat elements and attributes that they do not
+  understand as semantically neutral; leaving them in the DOM (for DOM
+  processors), and styling them according to CSS (for CSS processors),
+  but not inferring any meaning from them.</p>
+
   </div><h3 id="case-sensitivity-and-string-comparison"><span class="secno">2.3 </span>Case-sensitivity and string comparison</h3><p>This specification defines several comparison operators for
   strings.<p>Comparing two strings in a <dfn id="case-sensitive">case-sensitive</dfn> manner means
   comparing them exactly, code point for code point.<p>Comparing two strings in an <dfn id="ascii-case-insensitive">ASCII case-insensitive</dfn>

Received on Sunday, 24 May 2009 05:15:28 UTC