- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 02 Jan 2011 04:01:43 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv16058 Modified Files: Overview.html Log Message: Add some suggestions for how to do experimental events with vendor prefixes (whatwg r5737) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.4599 retrieving revision 1.4600 diff -u -d -r1.4599 -r1.4600 --- Overview.html 1 Jan 2011 06:33:58 -0000 1.4599 +++ Overview.html 2 Jan 2011 04:01:39 -0000 1.4600 @@ -3091,6 +3091,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 -->
Received on Sunday, 2 January 2011 04:01:45 UTC