Hi all,
In an other topic there was found that an incomplete end tag </td was 
the reason for an unexpected layout shift in IE.
http://archivist.incutio.com/viewlist/css-discuss/74402

Very, very strange is, that the html-validator did not remark this error.
The w3c-recommendations for html 4.01 say about the <td>: "Start tag: 
required, End tag: optional" [1]

    * But IMO that should not implicate that an incomplete (but not
      escaped) </td should be ignored totally when validating!
    * I checked the file with omitting the whole </td. Result: then IE
      is performing good also.

So I experimented with a very simple html-file with an unclosed end tag.

        <p>check incomplete end tag</p
        <p>next line</p>

http://home.tiscali.nl/developerscorner/css-discuss/check-incomplete-tag.htm

Now the results! :-)

    * The w3c html-validator says it is valid html (without warnings),
      but in the included source code we can see the tag in line 8 is
      really incomplete.
      
http://validator.w3.org/check?uri=http%3A%2F%2Fhome.tiscali.nl%2Fdeveloperscorner%2Fcss-discuss%2Fcheck-incomplete-tag.htm&ss=1
      
<http://validator.w3.org/check?uri=http%3A%2F%2Fhome.tiscali.nl%2Fdeveloperscorner%2Fcss-discuss%2Fcheck-incomplete-tag.htm&ss=1>
    * The WDG-validator says it is valid, but is giving a warning:
      
http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fhome.tiscali.nl%2Fdeveloperscorner%2Fcss-discuss%2Fcheck-incomplete-tag.htm&warnings=yes&input=yes&hidevalid=yes
      
<http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fhome.tiscali.nl%2Fdeveloperscorner%2Fcss-discuss%2Fcheck-incomplete-tag.htm&warnings=yes&input=yes&hidevalid=yes>
    * The online Tidy is giving a warning too:
      http://infohound.net/tidy/tidy.pl
    * But the Tidy extension in Firefox says it is 100% o.k.: no errors,
      no warnings.

Then I noticed, even weirder, the displayed code is ... browser dependent.

    * Firefox has a closing > at the beginning of the next line. That
      should be the reason why the build-in Tidy was so happy.
      See source code in FF:

<p>check incomplete end tag</p
><p>next line</p>

    * Double checked my uploaded file in ftp: viewed it in FileZilla.
      And still the same over there, without ending >: it is not the server.
    * Internet Explorer just plays the file as it is uploaded and on the
      server.
      See source code in IE6.
    * Source code in Opera 7.54 and Opera 8.01: nothing added, still
      incomplete.
    * Source code in Netscape 6.2 shows an interesting other way:

<p>check incomplete end tag</p>next line</p>.

    * And Mozilla 1.71: as FF. 
    * btw: Everything tested under Win98SE.

My conclusions and lessons:
Apparently different browsers have different "auto correcting machines" 
(or not) to handle incorrect html.
Extra reason to write good html...
And when strange differences occur between browsers: validate with 
different validators! Small warnings in one validator, ignored by an 
other validator, can have big consequences. Banging heads! ;-)

francky

[1] http://www.w3.org/TR/html4/struct/tables.html#h-11.2.6
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to