Although well meant, the advice to add onkeypress is misguided. This has been previously discussed, but: onclick is - despite its name - not device dependent (in the same way that, say, onmouseover is). onclick is really a misnomer for "onactivation". all modern browsers (if i remember correctly, any version 4+ browser) triggers onclick also when hitting the enter key.
the problem with adding onkeypress is that, on Mozilla/Firefox, even a "tab" triggers an onkeypress event. Now, if you imagine a user tabbing his/her way through a page of links, and one of them has an onkeypress, they'll activate it as they're simply moving from one link to the next...not good (particularly if the onkeypress is linked to some javascript that changes the current page location, for instance).


Moral of the story: only use onclick, and don't pair it up with onkeypress.

Patrick
_____________________________________________________
re�dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com

******************************************************
The discussion list for  http://webstandardsgroup.org/

Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************



Reply via email to