[giow] (0) use vendor--feature instead of _vendor-feature since Apple…

… engineers think underscores are ugly.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9590

git-svn-id: http://svn.whatwg.org/webapps@5307 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -3418,13 +3418,13 @@ <h4 id=extensibility><span class=secno>2.2.2 </span>Extensibility</h4>
 
   <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=""><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. 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. (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
   without risk of conflicting with future additions to the
   specification.</p>
 
@@ -3437,14 +3437,14 @@ <h4 id=extensibility><span class=secno>2.2.2 </span>Extensibility</h4>
    these features could write:</p>
 
    <pre>&lt;p&gt;This smells of lemons!
-&lt;span _ferret-smellovision _ferret-smellcode="LEM01"
-      _mb-outputsmell _mb-smell="lemon juice"&gt;&lt;/span&gt;&lt;/p&gt;</pre>
+&lt;span ferret--smellovision ferret--smellcode="LEM01"
+      mb--outputsmell mb--smell="lemon juice"&gt;&lt;/span&gt;&lt;/p&gt;</pre>
 
   </div>
 
-  <p>Attribute names starting with a U+005F LOW LINE character (_) are
-  reserved for user agent use and are guaranteed to never be formally
-  added to the HTML language.</p>
+  <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 class=note>Pages that use such attributes are by definition
   non-conforming.</p>

index

@@ -3342,13 +3342,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <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=""><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. 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. (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
   without risk of conflicting with future additions to the
   specification.</p>
 
@@ -3361,14 +3361,14 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    these features could write:</p>
 
    <pre>&lt;p&gt;This smells of lemons!
-&lt;span _ferret-smellovision _ferret-smellcode="LEM01"
-      _mb-outputsmell _mb-smell="lemon juice"&gt;&lt;/span&gt;&lt;/p&gt;</pre>
+&lt;span ferret--smellovision ferret--smellcode="LEM01"
+      mb--outputsmell mb--smell="lemon juice"&gt;&lt;/span&gt;&lt;/p&gt;</pre>
 
   </div>
 
-  <p>Attribute names starting with a U+005F LOW LINE character (_) are
-  reserved for user agent use and are guaranteed to never be formally
-  added to the HTML language.</p>
+  <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 class=note>Pages that use such attributes are by definition
   non-conforming.</p>

source

@@ -2347,15 +2347,16 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <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=""><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. 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. (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
   without risk of conflicting with future additions to the
   specification.</p>
@@ -2369,14 +2370,14 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    these features could write:</p>
 
    <pre>&lt;p>This smells of lemons!
-&lt;span _ferret-smellovision _ferret-smellcode="LEM01"
-      _mb-outputsmell _mb-smell="lemon juice">&lt;/span>&lt;/p></pre>
+&lt;span ferret--smellovision ferret--smellcode="LEM01"
+      mb--outputsmell mb--smell="lemon juice">&lt;/span>&lt;/p></pre>
 
   </div>
 
-  <p>Attribute names starting with a U+005F LOW LINE character (_) are
-  reserved for user agent use and are guaranteed to never be formally
-  added to the HTML language.</p>
+  <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 class="note">Pages that use such attributes are by definition
   non-conforming.</p>