[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Re: Ecmascript and Lynx/Linux

From: David Woolley
Subject: Re: lynx-dev Re: Ecmascript and Lynx/Linux
Date: Tue, 5 Feb 2002 22:51:27 +0000 (GMT)

> I'm forwarding this to the lynx-dev list.
[ Please forward to the other list; cross-posting mailing lists is not
a good idea. ]

The problem is not Ecmascript so much as:

- the document object model;
- the browser object model;
- Microsoft "marked safe for scripting" ActiveX controls.

None of these are specified by ECMA, and only some of the document
object model (see below) is specified by W3C; browser object models are
specific to browsers and ActiveX is Microsoft's technology.

> > correct; (2) turn to development of accessibility of Xwindows (am I
> > correct in the impression that javascript is being used in X with
> > graphically-oriented browsers or am I mistaken about this?), or (3) save

ECMAScript together with most of W3C Document Object Model level 1 and
a lot of of level 2 are implemented by Mozilla and therefore Netscape 6.
This also implements the ill defined Document Object Model 0, which is
essentially the document object model and browser object models from
early Netscapes.  Netscape 4 also runs on X and implements the Netscape
4 document and browser object models.

Mozilla does, I believe, have an accessibility sub-project, but this might
relate to the Microsoft Active Accessibility API.

However, the sort of sites that cause you problems are also likely
to fail on Mozilla, as they often mis-identify it as Netscape 4+ and
attempt to use the proprietory Netscape models rather than the W3C ones
(which are also supported by IE 5+).

> > regular occurrence for me to go to some site that was accessible a week or
> > two ago and find that it is now "new and improved"--and inaccessible.

Such sites are also denying themselves to people who, or whose emloyers,
are security conscious.  I've seen reports that there are 6 open security
holes in IE6 that are scripting related (most browser security problems
require scripting, even if the flaw is in ActiveX components).  I can
probably give you a URL for the USENET thread, but I can't verify the

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]