- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Wed, 9 Oct 2002 07:32:02 +0100 (BST)
- To: w3c-wai-ig@w3.org
> > Can I use JavaScript? Why not, it's a public ECMA standard. > > right but at the moment it is not a very usable standard for many machines > Using it also breaches a basic principle of computer security, that you do not run unverified executables. (In theory there may be sandboxing, but that sand boxing is being continually violated, in part because systems are just too "feature rich" to be able to understand well enough to lock down properly.) > to do and most users of it don't want it to do. (although I believe some > javascript support will be incorporated) A lot of the talk about supporting Javascript is about recognizing common idioms, rather than properly implementing browser and document object models. That would imply a continual need for maintenance as idioms change. Javascript, here, should be interpreted in the popular sense (i.e. that it includes document object models (not just W3C), browser object models and standard, pre-installed, "safe for scripting", ActiveX objects - this is somewhat similar to the popular definition of HTML, which includes all these, plus style sheets and Flash).
Received on Wednesday, 9 October 2002 02:32:07 UTC