[Top][All Lists]

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

Re: LYNX-DEV problem when page has only one input area

From: Foteos Macrides
Subject: Re: LYNX-DEV problem when page has only one input area
Date: Wed, 13 Nov 1996 14:27:55 -0500 (EST)

address@hidden (Larry W. Virden, x2487) wrote:
>> > The page in question is
>> >
>>      The HTML for that page is bad; there's no </FORM>.  Adding
>> either the </FORM>, or some other tag which implies the end of the
>> form (like <BODY>...</BODY>) fixes things.
>Is there no way that Lynx could be 'improved' to treat the end of file 
>while reading an HTML page as automatically closing any open constructs?

        I've already done that for FORM, and it will be in the next, but it's not as straightforward for some others,
and it interacts in complex ways with 'z'apping after some of
the document is received, such that only the received part is
rendered.  A global unwind of all open blocks could result in

        I wish FORMs had been implemented with less simpleminded
assumptions about what Lynx will be confronting, but, sigh...


 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

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