> Sure it does... *if* you want Lynx to handle JavaScript exactly
> the same as the big 2 . But that's not what he's proposing.
The proposal was not just Javascript support, but Javascript support
using the code from Mozilla.
> pretty unique. I can imagine a lot of simple JavaScript examples,
> like popups appearing as a link, or links, named [POPUP] in the
You are fighting a running battle against designers who, whilst they
often use cut and paste coding, sometimes do things different ways. That
means you have to continually update the list of Javascript idioms that
have to be recognised.
In the case of popups, although you can recognize ' onclick="popup(...",
as a likely popup, the parameter is usually not the link, and requires that
you also have interpreted parts of the function definition. Even if it
is text, it may be relative to a URL that is in the main part of the
function.
The common idiom of having a link that fills in a and submits a hidden
form is likely to be more difficult to treat in a shallow way.
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
