OnActivation would proberly be better to use, only reason i state to use onKeyPress is that validators moan if u dont use it.
But whatever way you activate the link, this is still the best way to get a pop up or a new page. On Fri, 26 Nov 2004 20:19 , Patrick H. Lauke <[EMAIL PROTECTED]> sent: >Mark Harwood >> Remeber to put onKeypress too > >I'd disagree. I've had this rant before, but here goes: onclick is not a >device specific handler. Onclick is also activated by the keyboard (e.g. >hitting return when focus is on a link). It's a misnomer, and should >really be "onactivation" or something. True, very old browsers may have >only had onclick triggered by the mouse, but these are very rare. In >addition, if somebody *was* using something like Netscape 4 and only >using the keyboard, with this method they'd still get to the linked >document, just that it won't pop up (as NN4.x is one of those that don't >consider the keyboard to give off onclick events). So, accessibility >wise, you're covered. > >Adding onkeypress can actually do more harm than good. Firefox (and I >think Mozilla as well) *correctly* interpret *all* keys as onkeypress, >even the TAB key. So, having something activate onkeypress will mean >that keyboard users won't be able to tab beyond that particular link. > >Patrick H. Lauke >-- >_____________________________________________________ >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/ > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
