000730 David Woolley wrote:
PW> it really shouldn't be difficult to get Lynx to recognise `onclick',
PW> extract the following URL & present it as a link marked `ONCLICK':
> In many, if not most, of the cases I've seen, the URL is not
> in the onclick parameter. What is there is either an index number,
> or only part of the relative URL; most commonly just an index number.
yes, that is true of the best public example i can offer.
to focus discussion, how could Lynx handle the document at
http://www.gotransit.com/fare/fndfare.asp ,
where getting a point-point bus fare is prevented by a [BUTTON] ?
the necessary URLs do seem to be present in the JS in the source,
but not necessarily in an easy-to-predict place.
anyone care to try the programming challenge?
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : [EMAIL PROTECTED]
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]