- From: Ignacio Javier <igjav@ctv.es>
- Date: Fri, 30 Apr 1999 09:55:18 +0200
- To: John Whelan <whelan@itp.unibe.ch>
- CC: www-html@w3.org
> > Thanks for replies, I assume putting somewhere: > > <a...href="javascript: > > is standard to that level, the html level (still obviously not at scripting > > level, but thet was not the question). > > In any event, you shouldn't use it, since it cripples the link for > users without Javascript enabled in their browsers. You should > instead put the appropriate 'http://' URI as the href attribute (at > least 95% of the uses of the 'javascript:' URI syntax are to open > another page in a jazzed-up window) and add an onclick attribute whose > value is whatever followed the 'javascript:', with ';return false' > tacked onto the end. It will have the same effect as the > 'javascript:' URI syntax for JS-enabled browsers, and also make the > link usable by the rest of the world. > > (I know this is off-topic, but if it prevents one person from breaking > another page with the 'javascript:' URI syntax, it'll be worth it.) Of course, and sure in IE4- and so for.... HTML 4.0 adds explicitly event support, of course and obviously. But the case is that discussing Javascript event model, apart from being non standard, is an another's list topic (try mozilla, but sure they are focusing on DOM). So about the topic only one thing more: the are *author tools* that ONLY allow explicitly one syntax for comms with html, that of the URI, so accesing them via this should be the only possible solution.
Received on Friday, 30 April 1999 03:55:01 UTC