> Exactly that is also my problem. Oky not mine but also a > customer of mine > wants the shift click. > Statement: Shift click does the same as click but opens in new window" > Problem: I have some functionality that changes a area you could name > display-area. The customer now argues that he expects the > display-area in a > new window.
My thoughts: - Thomas' statement: when onclick returns *false*, the href isn't taken. That solves many problems and I think was overlooked by critics of the href=# option. - href="#" won't go to the top of page if onclick returns false, however, href="javascript:void(0)" won't go anywhere no matter what the onclick event handler returns. - IE will open a window in any case if the SHIFT key is held down. I've found no way to suppress this, except perhaps href="javascript:window.close" ;-) (think of the downside to this) - Regarding the overuse of links to reach an event handler: I am one of those coders who overuses links for onclick items which do not need to be "links". I do this believing it will be better for a screen reader to understand. I may be off on this, but a screen reader "knows" a link is clickable. I'm not sure it knows an <img> is clickable, especially if the onclick is assigned dynamically. - Regarding comments on designing links which behave well when JavaScript isn't enabled: Some webs (e.g., the stuff we write) are run completely wrapped in a JavaScript portal, a.k.a. "Learning Management System". Designing links to perform favorably if JavaScript isn't enabled don't apply to our development work. The entire LMS would not run if JavaScript were not enabled. _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
