[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Re: Lynx interprets <a/> as </a>?
|
From: |
Klaus Weide |
|
Subject: |
Re: lynx-dev Re: Lynx interprets <a/> as </a>? |
|
Date: |
Wed, 15 Dec 1999 10:44:30 -0600 (CST) |
On Sun, 12 Dec 1999, David Woolley wrote:
> > The current modes apparently require the --> closing, unless
> > I'm missing something...? (Lynx 2.8.2. rel. 1)
>
> Assuming this hasn't changed since 2.7.2,
not AFAIK.
> in its most valid comments
> mode, Lynx requires >, following a correctly balanced -- and optional
> white space. I presume that dropping out of end_comment state is
> error recovery for the, obviously invalid, case of non-whitespace
> characters in this context. (It might also be a failure to make the
> code conditional on minimal mode.)
>
> To cope with your broken comments, you need historical mode, in which
> the > unconditionally terminates the comment.
Do you still consider current behavior in "Valid" mode a bug?
Klaus