On 26-Jun-2009, at 16:04, Adam Engst wrote:
> On Wed, Jun 24, 2009 at 3:41 PM, Edward Reid<edward

paleo.org> wrote:
>> At 6/20/2009 02:12 AM -0700, Adam Engst wrote:
>>>
>>> There are still some errors, but it looks like they fall into
>>> three categories, one of which is basically an unencoded ampersand
>>> and
>>> the other two of which look pretty minor as well.
>>
>> Minor as in easy to fix, yes (though I don't understand one of them).
>> Minor in their effects on the predictability of rendering, no. As I
>> understand it (and I don't claim to be an expert here), even minor
>> errors throw the browser out of standards mode and into quirks mode.
>> "Almost standard" is the same as "not standard".
>
> Does anyone have any hard information on this "quirks" mode and how
> we'd know if our site was causing browsers to go into it? IE6 is low
> on our priority list, but my understanding is that our site renders
> fine in all modern browsers, particularly those on the Mac.
The Web Developer bar in Firefox will tell you if a site is in quirk
mode (a ~ on the bar) or in compliance mode (a check mark in the same
place). Here's a picture of the bar in both states:
http://home.kreme.com/quirks.html
For the record, TidBITS.com renders in compliant mode.