lynx-dev TagSoup (was: bad sites (was bug report))

[Leonid Pauzner]

>      * From: Philip Webb <address@hidden>
>      * Date: Sun, 18 Oct 1998 23:54:25 -0400 (EDT)
>      * Cc: address@hidden


>> on the first page there is a list of news
>> & near each item is written a time when it came.
>> In Netscape you are able to click on any news string,
>> but Lynx does not think it is a link.

> this is a different problem entirely, bad HTML:
> there's an  <LI>  within the  <A> ... </A> , which offends normal Lynx.
> to get around this, execute  lynx -tagsoup http://www.rbc.ru/news_fp.shtml ,
> which tries to handle this type of badly written site: it works for me.
> you could send a polite note to the author too.

Apperently, there is no comments on TagSoup mode anywhere in lynx help, SHOULD 
BE.
As I understand it made an alternative parsing for broken HTML pages,
but few exact words still necessary...
In this certain case, the markup inside <A>... </A>, Lynx should resolve
this anchor by default because it is highly unlikely for user
to lost the link when it is present with Netscape/MSIE
(see the second Note below, it is just a recomendation).
Also, this is the second report on last week, the first person said
no problem with 2.7.2


HTML 4.0 said:
~~~~~~~~~~~~~~
   Note: User agents should be able to find anchors created by empty A
   elements, but some fail to do so. For example, some user agents may
   not find the "empty-anchor" in the following HTML fragment:
<A name="empty-anchor"></A>
<EM>...some HTML...</EM>
<A href="#empty-anchor">Link to empty anchor</A>

   Note. We recommend that authors not make markup the content of an
   anchor. Thus:
<H1><A name="xxx">My Heading</A></H1>

   is preferred to:
<A name="xxx"><H1>My Heading</H1></A>