On Wednesday, November 10, 2004 6:47 AM, Patrick Lauke wrote: > > Incidentally, I've discussed this before, but...onclick is > implemented in practically all current browsers as a > non-device-specific event, as it is triggered by keyboard > access as well (on elements that can receive focus via > keyboard tabbing, anyway, i.e. links and form elements).
Patrick is, as usual, bang on with this. Further - unless it is done very carefully, onkeypress redundancy makes keyboard navigation next to impossible in various browsers. In many cases it causes unintended consequences - like not allowing one to tab to the next link, causing popups to occur, or changing stylesheets without the user really wanting to change stylesheets. Best regards, Derek. -- Derek Featherstone [EMAIL PROTECTED] phone: 613.599.9784; toll-free: 1.866.932.4878 (North America) Web Accessibility: http://www.wats.ca Personal: http://www.boxofchocolates.ca ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
