[] (0) Add some suggestions for how to do experimental events with ve…

…ndor prefixes

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

complete.html

@@ -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 &mdash; 1 January 2011</h2>
+    <h2 class="no-num no-toc">Draft Standard &mdash; 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 @@ <h4 id=extensibility><span class=secno>2.2.2 </span>Extensibility</h4>
   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 -->

index

@@ -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 &mdash; 1 January 2011</h2>
+    <h2 class="no-num no-toc">Draft Standard &mdash; 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 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   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 -->

source

@@ -2461,6 +2461,20 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   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 -->