[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sun, 29 Apr 2001 21:41:46 +0100 (BST)
> protocol specification.
IE and NS4 browser/document object models), but:
available as PDF files on their web site.
Internet Explorer's object model (and possibly a definition of JScript)
are available from their MSDN web site.
The W3C's document object models are available from w3c.org. This only
covers documents, not browser automation.
NS6 uses ECMA Script as the core language, with parts of the W3C document
model and proprietory browser and document models based on the de facto
common ground between IE and NS4.
As far as I know, Lynx's document and browser object models are not
documented, and not exposed in a form that is optimised for scripting.
Although NS6 is trying to allow sites to work with W3C and ECMA standards
only, this doesn't cover browser automation, which is one of the main
code dependent on the browser they think that they are running on - more
user agent lies.
A significant amount of commercial scripting relies on a full implementation
of frames, and some of the common problem code is associated with
simultaneious display of popup and main windows.
There is some trend towards automating style sheets to obtain the desired
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden