[html5] r5737 - [] (0) Add some suggestions for how to do experimental events with vendor prefixes

[whatwg at whatwg.org]

Author: ianh
Date: 2011-01-01 20:01:33 -0800 (Sat, 01 Jan 2011)
New Revision: 5737

Modified:
   complete.html
   index
   source
Log:
[] (0) Add some suggestions for how to do experimental events with vendor prefixes

Modified: complete.html
===================================================================
--- complete.html	2011-01-01 06:33:52 UTC (rev 5736)
+++ complete.html	2011-01-02 04:01:33 UTC (rev 5737)
@@ -221,7 +221,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 1 January 2011</h2>
+    <h2 class="no-num no-toc">Draft Standard — 2 January 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -3487,6 +3487,19 @@
   members should be prefixed by vendor-specific strings to prevent
   clashes with future versions of this specification.</p>
 
+  <p>For events, experimental event names should be prefixed with
+  vendor-specific strings.</p>
+
+  <div class=example>
+
+   <p>For example, if a user agent called "Pleas<!--e h-->old" were to
+   add an event to indicate when the user is going up in an elevator,
+   it could use the prefix "<code title="">pleasold</code>" and thus
+   name the event "<code title="">pleasoldgoingup</code>", possibly
+   with an event handler attribute named "<code title="">onpleasoldgoingup</code>".</p>
+
+  </div>
+
   <p>All extensions must be defined so that the use of extensions
   neither contradicts nor causes the non-conformance of functionality
   defined in the specification.</p> <!-- thanks to QA Framework -->

Modified: index
===================================================================
--- index	2011-01-01 06:33:52 UTC (rev 5736)
+++ index	2011-01-02 04:01:33 UTC (rev 5737)
@@ -225,7 +225,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard — 1 January 2011</h2>
+    <h2 class="no-num no-toc">Draft Standard — 2 January 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -3466,6 +3466,19 @@
   members should be prefixed by vendor-specific strings to prevent
   clashes with future versions of this specification.</p>
 
+  <p>For events, experimental event names should be prefixed with
+  vendor-specific strings.</p>
+
+  <div class=example>
+
+   <p>For example, if a user agent called "Pleas<!--e h-->old" were to
+   add an event to indicate when the user is going up in an elevator,
+   it could use the prefix "<code title="">pleasold</code>" and thus
+   name the event "<code title="">pleasoldgoingup</code>", possibly
+   with an event handler attribute named "<code title="">onpleasoldgoingup</code>".</p>
+
+  </div>
+
   <p>All extensions must be defined so that the use of extensions
   neither contradicts nor causes the non-conformance of functionality
   defined in the specification.</p> <!-- thanks to QA Framework -->

Modified: source
===================================================================
--- source	2011-01-01 06:33:52 UTC (rev 5736)
+++ source	2011-01-02 04:01:33 UTC (rev 5737)
@@ -2461,6 +2461,20 @@
   members should be prefixed by vendor-specific strings to prevent
   clashes with future versions of this specification.</p>
 
+  <p>For events, experimental event names should be prefixed with
+  vendor-specific strings.</p>
+
+  <div class="example">
+
+   <p>For example, if a user agent called "Pleas<!--e h-->old" were to
+   add an event to indicate when the user is going up in an elevator,
+   it could use the prefix "<code title="">pleasold</code>" and thus
+   name the event "<code title="">pleasoldgoingup</code>", possibly
+   with an event handler attribute named "<code
+   title="">onpleasoldgoingup</code>".</p>
+
+  </div>
+
   <p>All extensions must be defined so that the use of extensions
   neither contradicts nor causes the non-conformance of functionality
   defined in the specification.</p> <!-- thanks to QA Framework -->