W3C home > Mailing lists > Public > www-html-editor@w3.org > October to December 1998

Re: Markup errors in 4.0 spec....

From: Ian Jacobs <ij@w3.org>
Date: Wed, 11 Nov 1998 17:31:22 -0500
Message-ID: <364A103A.482576CE@w3.org>
To: david_harmon@ibi.com
CC: www-html-editor@w3.org
david_harmon@ibi.com wrote:
>      I am reading the (downloaded) HTML 4.0 spec, under IE 3.02.  Several
>      times, reading through the spec, I've found places where the emphasis
>      (green on my system) of a note does not end with the note, but
>      continues until some other factor ends it.
>      I have examined one of these, specifically the first note under
>      section 17.2.1, Control Types.  In this case, the bug appears to be
>      caused by having an unclosed paragraph element within the note's DIV
>      element, but outside the EM element.  Adding a </P> in the obvious
>      place fixes the emphasis, but adds an extra line under the note.
>      Removing the <P> also fixes the emphasis, and leaves the usual
>      (single) spacing after (and before) the note.  The spec itself only
>      states that the closing tag for P is optional.  Oddly, I cannot seem
>      to duplicate this in a smaller file of my own.  I do not know whether
>      this bug still happens in IE 4.01.


This is not a markup error within the specification, but (apparently) a
in IE 3.02. The markup in question in section 17.2.1 is:

   <div class="note"><P>
   <em><strong>Note.</strong> Authors should note that the
<a                                   href="forms.html#edef-BUTTON"
   class="einst">BUTTON</samp></a> element offers richer 
   rendering capabilities than the <a href="forms.html#edef-INPUT"
class="noxref"><samp     class="einst">INPUT</samp></a> 

The P element is closed by the DIV end tag. As the SGML tutorial
states: "an end tag closes, back to the matching start tag,
all unclosed intervening start tags with omitted end tags."

>      While I'm here:  This version of IE does not accept multiple STYLE
>      elements in the HEAD, as appears in some styling examples.  Only the
>      last one is effective.  I have worked around this by combining all the
>      CSS code into one STYLE element.  A friend has verified that this bug
>      does not appear in 4.01.  I'm not sure what you folks do about cases
>      like that....
>      In neither case do I know whether the bug appears in Netscape.

W3C does not track browser bugs. You should bring these points
to the attention of Microsoft.

Thank you for contacting us,

 - Ian

Ian Jacobs (jacobs@w3.org) 
Received on Wednesday, 11 November 1998 17:31:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:08:20 UTC