- From: Doug Gibson <doug@dgibson.net>
- Date: Sat, 9 Oct 2004 14:07:05 -0400
- To: "'WAI GL \(E-mail\)'" <w3c-wai-gl@w3.org>
Can anyone refresh me on why we don't just use onclick (I probably missed those discussions)? As far as I know, the keyboard has always fired the onclick event at least on links and buttons. Does it not work this way in certain user agents or is it against spec that it does work that way? Thanks, Doug Gibson -----Original Message----- From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Martin Honnen Sent: Saturday, October 09, 2004 9:40 AM To: 'WAI GL (E-mail)' Subject: [script techniques] onactivate not valid HTML 4.01/XHTML 1.0 [Was: Re: Updated Internal Drafts Published] Ben Caldwell wrote: > Just a quick note to let everyone know that the latest round of internal working drafts has been published. > Scripting Techniques for WCAG 2.0 > http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-SCRIPT-TECHS-20041008/ That draft in http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-SCRIPT-TECHS-20041008/#dom-act ivate suggests to use an onactivate event handler in HTML 4.01/XHTML 1.0 markup, giving the following example: <p><a href="menu.php" onactivate="checkForCookie()">main menu</a></p> however I think that is wrong as that is neither valid HTML 4.01 nor valid XHTML 1.0. If you look at the HTML 4.01 specification then it defines event handler attributes in http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.3 and you do not find onactivate there. It doesn't make much sense then to have a script techniques example suggesting to use an attribute that is not part of HTML 4. -- Martin Honnen http://JavaScript.FAQTs.com/
Received on Saturday, 9 October 2004 18:07:14 UTC