Re: new anchor type?

Marcus E. Hennecke (marcush@crc.ricoh.com)
Mon, 1 Jul 1996 09:49:35 -0700 (PDT)


Date: Mon, 1 Jul 1996 09:49:35 -0700 (PDT)
From: "Marcus E. Hennecke" <marcush@crc.ricoh.com>
Message-Id: <199607011649.JAA06608@cougar.crc.ricoh.com>
To: www-html@w3.org
Subject: Re: new anchor type?

On Sun, 30 Jun 1996 02:02:24 +0900, Ka-Ping Yee <s-ping@orange.cv.tottori-u.ac.jp> wrote:
> It's a pity that Netscape...
> 
>     - doesn't support the ID attribute.
>     - doesn't support the FN tag.
>     - still parses comments wrong.
>     - lets incorrect markup pass as okay.
>     - flags correct markup as wrong, and makes it blink.
>     - encourages people to use bad markup by
>           endorsing SIZE=+5 and BGCOLOR=#343434.
>     - doesn't support SRC in HR or UL or LI tags.
>     - leaves blank lines for multiple BR tags.
>     - doesn't support LH.
>     - never bothered to do FIGures or OVERLAYs.
>     - doesn't let you at the information in any LINK tags.
>     - doesn't support stylesheets.
> 
> (Anyone else care to add to this list?

Sure:

 - doesn't support the CLEAR attribute on any block elements (only BR)
 - doesn't support ALIGN=CENTER for tables
 - doesn't support ALIGN=JUSTIFY (ok, no other browser does, either)
 - doesn't support &shy; (Thomas Reardon, are you listening? This could
   be something real cool: Don't display &shy; as Netscape does but do
   allow line breaks there. Only if a line break occurs, display the
   hyphen. This would be a very simple, yet effective hyphenation
   algorithm and you would be the first to offer that.)
 - doesn't support orphan and widow control on print-out

The 3.0b5 version now actually does support <U>underlined text</U>.

Marcus E. Hennecke
marcush@crc.ricoh.com        http://www.crc.ricoh.com/~marcush/