I just don't understand what compells developers to actually create
embedded web applications that omit such basic required elements as #
signs.
In article <[EMAIL PROTECTED]>,
Jason Johnston <[EMAIL PROTECTED]> wrote:
> I noticed that the DOCTYPE changes have caused Microsoft Outlook Web
> Access to no longer be subject to quirks. It uses the following DOCTYPE:
>
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 3.2//EN">
>
> with color values specified in the body tag:
> <body TEXT=000000 BGCOLOR=FFFFFF LINK=000000 ALINK=000000 VLINK=000000>
>
> Before this weekend, the absence of the "#" in the color values was
> ignored and links were black. Now, links are the default link color
> (blue) because strict mode ignores these invalid color values. Deleting
> the DOCTYPE completely causes the quirks behavior to return.
>
> The public identifier "-//IETF//DTD HTML 3.2//EN" needs to be added to
> the current list to emulate past behavior.
>
> Thanks
> --J
>
>
> David Baron wrote:
>
> > I just checked in (on the trunk) some changes to the DOCTYPE handling
> > code. (They should be in any builds after, but not including,
> > 2001-09-08-14.) The purpose of these changes is to make our DOCTYPE
> > handling forward-compatible. The old code generally used a list of
> > known patterns in DOCTYPE declarations to determine that a page should
> > be displayed using strict mode, and otherwise used quirks mode. The new
> > code uses the presence of one of a set of known public identifiers, or
> > the lack of a DOCTYPE declaration, to determine that a page should be
> > displayed using quirks mode, and otherwise uses strict mode.
> >
> > These changes are not intended to change the mode that is used for
> > DOCTYPE declarations in common use on the Web (except in a few known
> > cases where the lack of future-compatibility had already become a lack
> > of present-compatibility). However, since the new code is based on a
> > list of known DOCTYPE declarations that should trigger quirks mode,
> > there are probably a few that we need in the list that were omitted.
> > This means that the changes will probably cause a few regressions.
> >
> > If you notice any regressions in the layout of sites in builds starting
> > this weekend that may be related to this change, please let me know, so
> > that I can add the necessary public identifiers to the list (in
> > nsParser.cpp) or make other tweaks, if necessary.
> >
> > -David
> >
> >
>
