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

[Foteos Macrides]

Wayne Buttles <address@hidden> wrote:
>On Wed, 13 Nov 1996, Foteos Macrides wrote:
>
>> >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
>> lynx2-6mods.zip, 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
>> crashes.
>> 
>
>I don't know about a complete unwind, but a /body and /html would be cool
>with a check for open form on /body or /html.  Fote, could I see the diff
>on that form closing code, or can you point me to where you implemented it
>in the source?

        I got rid of the FORM-specific unwind and did set up a complete
unwind for all open containers on EOF.  It seems to be adequately crash
proof.  At least, I've been 'z'apping it left and right without any
crashes. :) :) :)

        I put out a new lynx2-6mods.zip.  The relevant changes are in
SGML_free() of SGML.c.

                                Fote

=========================================================================
 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.
;