Re: <IMAGE>? <TT> == <I>? toHell(NS)

David Perrell (davidp@earthlink.net)
Tue, 29 Oct 1996 18:42:11 -0800


Message-Id: <199610300242.SAA21783@austria.it.earthlink.net>
From: "David Perrell" <davidp@earthlink.net>
To: "Carl Morris" <msftrncs@htcnet.com>, "WWW HTML List" <www-html@w3.org>
Subject: Re: <IMAGE>? <TT> == <I>? toHell(NS)
Date: Tue, 29 Oct 1996 18:42:11 -0800

Carl Morris wrote:
> Thank goodness, your logic isn't working today.  Think about what you
> said and please tell me we are not talking about the same thing.

Perhaps we are not. You're attempting to apply logic based on rules of
markup. I'm attempting to apply logic to the treatment of cases where
the rules are broken and yet there is logic in the construct that
breaks them. There is no logic in <I>italic text</B>, but there is in

> <TT>hello <I>good-bye</TT> maybe?</I>

if the text can be both monospaced and italic. Just because <TT>hello
<I>good-bye</TT> maybe?</I> is invalid HTML, logic does not dictate
that </TT> must always indicate the end of an italicized section. The
3.2 ref spec calls for start and end tags for all text and phrase
markup.

(As you probably know, IE treats overlapping (not nested) italic and
bold text as you suggest, and will terminate an <I> with an unmatched
</B> and vice versa. So IE's isolated agreement with my logic is
probably a bug as far as they're concerned.)

> ...  I want the browser I use
> to help me find errors...

Terminating one tag with a different end tag is bad guessing that is
unlikely to help find errors. It was IE's logical (IMO) refusal to
terminate <TT> with </I> that started this thread.

> ... the thing MSIE is relaxed on, NN screws up ...

As has been pointed out in other messages, the same brand of browser
behaves differently on different platforms and with different versions.

Maybe a suggestion of how to treat bad markup in the spec is a good
idea. Consider this thread and don't rely on logic and common sense to
prevail (whoever's right).

David Perrell