[html5] r5562 - [] (0) Change how vendor extensions are marked up. Fixing http://www.w3.org/Bugs [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Sep 29 15:38:15 PDT 2010


Author: ianh
Date: 2010-09-29 15:38:14 -0700 (Wed, 29 Sep 2010)
New Revision: 5562

Modified:
   complete.html
   index
   source
Log:
[] (0) Change how vendor extensions are marked up.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9590

Modified: complete.html
===================================================================
--- complete.html	2010-09-29 22:28:00 UTC (rev 5561)
+++ complete.html	2010-09-29 22:38:14 UTC (rev 5562)
@@ -3382,13 +3382,13 @@
 
   <p>For markup-level features that are intended for use with
   <a href=#syntax>the HTML syntax</a>, extensions should be limited to new
-  attributes of the form "<code title=""><var title="">vendor</var>--<var title="">feature</var></code>", where
+  attributes of the form "<code title="">x0<var title="">vendor</var>-<var title="">feature</var></code>", where
   <var title="">vendor</var> is a short string that identifies the
-  vendor responsible for the extension, and <var title="">feature</var> is the name of the feature. (Note the use of
-  <em>two</em> hyphens in the name.) New element names should not be
-  created. Using attributes for such extensions exclusively allows
-  extensions from multiple vendors to co-exist on the same element,
-  which would not be possible with elements. Using the "<code title=""><var title="">vendor</var>--<var title="">feature</var></code>" form allows extensions to be made
+  vendor responsible for the extension, and <var title="">feature</var> is the name of the feature. New element names
+  should not be created. Using attributes for such extensions
+  exclusively allows extensions from multiple vendors to co-exist on
+  the same element, which would not be possible with elements. Using
+  the "<code title="">x-<var title="">vendor</var>-<var title="">feature</var></code>" form allows extensions to be made
   without risk of conflicting with future additions to the
   specification.</p>
 
@@ -3401,14 +3401,16 @@
    these features could write:</p>
 
    <pre><p>This smells of lemons!
-<span ferret--smellovision ferret--smellcode="LEM01"
-      mb--outputsmell mb--smell="lemon juice"></span></p></pre>
+<span x-ferret-smellovision x-ferret-smellcode="LEM01"
+      x-mb-outputsmell x-mb-smell="lemon juice"></span></p></pre>
 
   </div>
 
-  <p>Attribute names containing two consecutive U+002D HYPHEN-MINUS
-  (-) characters are reserved for user agent use and are guaranteed to
-  never be formally added to the HTML language.</p>
+  <p>Attribute names beginning with the two characters "<code title="">x-</code>" are reserved for user agent use and are
+  guaranteed to never be formally added to the HTML language. For
+  flexibility, attributes names containing underscores (the U+005F LOW
+  LINE character) are also reserved for experimental purposes and are
+  guaranteed to never be formally added to the HTML language.</p>
 
   <p class=note>Pages that use such attributes are by definition
   non-conforming.</p>
@@ -3434,6 +3436,11 @@
 
   </div>
 
+  <p>When adding new <a href=#reflect title=reflect>reflecting</a> IDL
+  attributes corresponding to content attributes of the form "<code title="">x-<var title="">vendor</var>-<var title="">feature</var></code>", the IDL attribute should be named
+  "<code title=""><var title="">vendor</var><var title="">Feature</var></code>" (i.e. the "<code title="">x</code>"
+  is dropped from the IDL attribute's name).</p>
+
   <hr><p>When vendor-neutral extensions to this specification are needed,
   either this specification can be updated accordingly, or an
   extension specification can be written that overrides the

Modified: index
===================================================================
--- index	2010-09-29 22:28:00 UTC (rev 5561)
+++ index	2010-09-29 22:38:14 UTC (rev 5562)
@@ -3359,13 +3359,13 @@
 
   <p>For markup-level features that are intended for use with
   <a href=#syntax>the HTML syntax</a>, extensions should be limited to new
-  attributes of the form "<code title=""><var title="">vendor</var>--<var title="">feature</var></code>", where
+  attributes of the form "<code title="">x0<var title="">vendor</var>-<var title="">feature</var></code>", where
   <var title="">vendor</var> is a short string that identifies the
-  vendor responsible for the extension, and <var title="">feature</var> is the name of the feature. (Note the use of
-  <em>two</em> hyphens in the name.) New element names should not be
-  created. Using attributes for such extensions exclusively allows
-  extensions from multiple vendors to co-exist on the same element,
-  which would not be possible with elements. Using the "<code title=""><var title="">vendor</var>--<var title="">feature</var></code>" form allows extensions to be made
+  vendor responsible for the extension, and <var title="">feature</var> is the name of the feature. New element names
+  should not be created. Using attributes for such extensions
+  exclusively allows extensions from multiple vendors to co-exist on
+  the same element, which would not be possible with elements. Using
+  the "<code title="">x-<var title="">vendor</var>-<var title="">feature</var></code>" form allows extensions to be made
   without risk of conflicting with future additions to the
   specification.</p>
 
@@ -3378,14 +3378,16 @@
    these features could write:</p>
 
    <pre><p>This smells of lemons!
-<span ferret--smellovision ferret--smellcode="LEM01"
-      mb--outputsmell mb--smell="lemon juice"></span></p></pre>
+<span x-ferret-smellovision x-ferret-smellcode="LEM01"
+      x-mb-outputsmell x-mb-smell="lemon juice"></span></p></pre>
 
   </div>
 
-  <p>Attribute names containing two consecutive U+002D HYPHEN-MINUS
-  (-) characters are reserved for user agent use and are guaranteed to
-  never be formally added to the HTML language.</p>
+  <p>Attribute names beginning with the two characters "<code title="">x-</code>" are reserved for user agent use and are
+  guaranteed to never be formally added to the HTML language. For
+  flexibility, attributes names containing underscores (the U+005F LOW
+  LINE character) are also reserved for experimental purposes and are
+  guaranteed to never be formally added to the HTML language.</p>
 
   <p class=note>Pages that use such attributes are by definition
   non-conforming.</p>
@@ -3411,6 +3413,11 @@
 
   </div>
 
+  <p>When adding new <a href=#reflect title=reflect>reflecting</a> IDL
+  attributes corresponding to content attributes of the form "<code title="">x-<var title="">vendor</var>-<var title="">feature</var></code>", the IDL attribute should be named
+  "<code title=""><var title="">vendor</var><var title="">Feature</var></code>" (i.e. the "<code title="">x</code>"
+  is dropped from the IDL attribute's name).</p>
+
   <hr><p>When vendor-neutral extensions to this specification are needed,
   either this specification can be updated accordingly, or an
   extension specification can be written that overrides the

Modified: source
===================================================================
--- source	2010-09-29 22:28:00 UTC (rev 5561)
+++ source	2010-09-29 22:38:14 UTC (rev 5562)
@@ -2359,16 +2359,15 @@
 
   <p>For markup-level features that are intended for use with
   <span>the HTML syntax</span>, extensions should be limited to new
-  attributes of the form "<code title=""><var
-  title="">vendor</var>--<var title="">feature</var></code>", where
+  attributes of the form "<code title="">x0<var
+  title="">vendor</var>-<var title="">feature</var></code>", where
   <var title="">vendor</var> is a short string that identifies the
   vendor responsible for the extension, and <var
-  title="">feature</var> is the name of the feature. (Note the use of
-  <em>two</em> hyphens in the name.) New element names should not be
-  created. Using attributes for such extensions exclusively allows
-  extensions from multiple vendors to co-exist on the same element,
-  which would not be possible with elements. Using the "<code
-  title=""><var title="">vendor</var>--<var
+  title="">feature</var> is the name of the feature. New element names
+  should not be created. Using attributes for such extensions
+  exclusively allows extensions from multiple vendors to co-exist on
+  the same element, which would not be possible with elements. Using
+  the "<code title="">x-<var title="">vendor</var>-<var
   title="">feature</var></code>" form allows extensions to be made
   without risk of conflicting with future additions to the
   specification.</p>
@@ -2382,14 +2381,17 @@
    these features could write:</p>
 
    <pre><p>This smells of lemons!
-<span ferret--smellovision ferret--smellcode="LEM01"
-      mb--outputsmell mb--smell="lemon juice"></span></p></pre>
+<span x-ferret-smellovision x-ferret-smellcode="LEM01"
+      x-mb-outputsmell x-mb-smell="lemon juice"></span></p></pre>
 
   </div>
 
-  <p>Attribute names containing two consecutive U+002D HYPHEN-MINUS
-  (-) characters are reserved for user agent use and are guaranteed to
-  never be formally added to the HTML language.</p>
+  <p>Attribute names beginning with the two characters "<code
+  title="">x-</code>" are reserved for user agent use and are
+  guaranteed to never be formally added to the HTML language. For
+  flexibility, attributes names containing underscores (the U+005F LOW
+  LINE character) are also reserved for experimental purposes and are
+  guaranteed to never be formally added to the HTML language.</p>
 
   <p class="note">Pages that use such attributes are by definition
   non-conforming.</p>
@@ -2417,6 +2419,14 @@
 
   </div>
 
+  <p>When adding new <span title="reflect">reflecting</span> IDL
+  attributes corresponding to content attributes of the form "<code
+  title="">x-<var title="">vendor</var>-<var
+  title="">feature</var></code>", the IDL attribute should be named
+  "<code title=""><var title="">vendor</var><var
+  title="">Feature</var></code>" (i.e. the "<code title="">x</code>"
+  is dropped from the IDL attribute's name).</p>
+
   <hr>
 
   <p>When vendor-neutral extensions to this specification are needed,




More information about the Commit-Watchers mailing list