(may contain sarcasm)

If you’re using a browser that doesn’t support javascript, go back to the early 90’s and stay there.

But here is the problem I am facing. I have an onclick event handler for an anchor element (its a menu) but I dont want the onclick event handler to be invoked by pressing enter. Since all the methods suggested here to make the anchor accessible (href=javascript:;, href=javascript:void(null), href=#) seem to reset the focus on the address (in IE atleast). I can catch the event through onkeypress handler adn check for a enter key and return false, but somehow the onclick event is being invoked after the onkeypress event even if I return false in onkeypress. and by the time it reaches the onclick event the keycode is lost. so, is there a way to prevent firing of onclick event from within onkeypress event?

Thanks

I must still be missing something here then.

whenever I put href=”#” in any link (static or dynamically generated), it scrolls me to the top of the screen… Even if I add return false; to my added eventListener(s).

Edit Yes, you do. The return false must be in the function that was added via the event listeners. It might be more helpful to give a URL and check if there are other errors.

The first step is to generate links that only work with JavaScript via JavaScript (createElement). Then you set the href to #, or - even better - link them to a real target that makes sense and instruct the script that gets applied via the handler NOT to follow the link by ending it in return false in DOM1 or use a bespoke stopPropagation function in DOM2. Safari, however does not really follow the common ways to stop from following the links and needs an extra onclick return false.

Check the examples in the node cloning post to see what I mean.

For DOM1 instructions, check chapter 3 of the unobtrusive JavaScript course

Opera jumps from link to link via the A key, not tab.