[thelist] What is wrong with this site?

[Joe LaChapell]

I think we have basic philosophical differences.  You see a browser 
"protecting" the user by assuming a closing table tag (for example), I 
see bloated browsers to support a developer who doesn't know how to 
markup correctly, which in the end harms end users.

I guess I put more onus on the developer.  For example, I don't think 
that support for a missing semicolon should be added to Java compilers. 
  XML parsers are another example.

Anyway, cheers!
-joe

Jeff Howden wrote:

> joe,
> 
> 
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>From: Joe LaChapell
>>
>>The content type is text/plain ... therefore somebody
>>wants the output to be text/plain.  IE is changing this
>>to display as text/html, which may not be the intended
>>output, but IE says that it "should" be.  End users and
>>developers alike should think this is horribly wrong.
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> 
> again, as evidenced by the original request, the developer doesn't always
> intend for their work to be sent as text/plain.  ie is doing its best to
> protect the user from this mistake.
> 
> 
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>IE is overriding the developers intended output.  You
>>don't see this as a problem? What other assumptions can
>>be made that are "good" for the end user?
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> 
> closing tables with missing </table> tags.
> 
> closing fieldsets with missing </fieldset> tags.
> 
> .jeff
> 
> ------------------------------------------------------
> Jeff Howden - Web Application Specialist
> Resume - http://jeffhowden.com/about/resume/
> Code Library - http://evolt.jeffhowden.com/jeff/code/
> 
>