Re: title

Carl Morris (msftrncs@htcnet.com)
Sun, 22 Sep 1996 17:07:11 -0500


Message-Id: <199609222210.RAA26016@inet.htcnet.com>
From: "Carl Morris" <msftrncs@htcnet.com>
To: <smishra@cc.gatech.edu>
Cc: "WWW HTML List" <www-html@w3.org>
Subject: Re: title
Date: Sun, 22 Sep 1996 17:07:11 -0500

| The others (HEAD and HTML) can be inferred from context. In the
parser I
| have put together, if TITLE (or BASE or LINK or STYLE) is seen, HEAD
and
| HTML are automatically inserted. Also, HEAD is closed as soon as a
non-head
| element (or </HEAD>) is encountered. So, making HEAD optional does
not
| cause problems.

I guess the problem with this is I have seen way too many people use
STYLE and SCRIPT in the BODY...  do you then ignore them (sence you
probably have no use for them anyway yet>)

What doi you do if you encounter stray text in the head?

<HEAD>
	Does this screw anything up?
</HEAD>

I know MSIE and NETSCAPE both will display the text as part of a
paragraph... annoying sometimes specially before MSIE supported SCRIPT
and STYLE...

| MSIE then is not paying attention to mime types, a major bug. Even if
a
| document has a .html extension, if it is delivered with mime-type
| text/plain, it should be rendered as plain text, not HTML.

No, its paying attention... but checks for errors in mime
configuration, since TEXT/PLAIN is generic type used by servers when
they have to guess... MSIE trys then to guess by extension of the file
and then content...  this was done to cure the rash of server admins
who refuse to add types for MIDI and newer graphical formats...  I
think they may have gone overboard with the TXT file example, and I
have yet more testing to do...