Re: JavaScript

On Thu, 29 May 2003 17:59:50 -0400, Andy Edmonds wrote:

>In fact, the Gecko/Mozilla/Netscape javascript implementation is
>becoming the reference. The js engine, "Rhino", is easily embeddable and
>drives the scripting engine for hundreds of projects beyond web
>browsers.
>

>The key is to use w3c standard methods like document.getElementById and
>not IE proprietary methods like document.all.
>
It seems to me that IF you can afford to work only on relatively recent
browsers, they will all work OK with js so long as it does follow
standards (maybe one or tweaks needed?), and of course, if js isn't
turned off.


>That said, you will need an alternate strategy for text only/handheld
>device browsers -- but you'll need that even if you don't use
>javascript.
>
Quite. The use or not of js is just one of a host of issues when
designing for platforms such as kiosks and handhelds.

The issue about the voice browser not coping with js is a significant
one. Does anyone know if it is likely to be compliant in the future, or
even if it's possible?

Isn't there an issue if sites build to standards, but no-one makes a
standards-compliant voice browser, yet the law (potentially) says that
sites have to work with voice browsers?

*    Nick Gassman - eCommerce Manager - [email protected]     *
              * http://ba.com *

    --------------------------------------------------------------
     POSTINGS (in plain text): [email protected]
           SUBSCRIPTION CHANGES:  http://lists.syntagm.co.uk
            (or send email to mailto:[email protected])
    --------------------------------------------------------------