Re: safari rendering bug: site display not correct

In article <warren.oates-0B4763.10223730122005@xxxxxxxxxxxxxxxxxxx>,
Warren Oates <warren.oates@xxxxxxxxx> wrote:


> You're right. In 'quirks mode' Safari should stop rendering boldface
> when it sees </b>. It would make sense. On the other hand, what doctype
> does the site in question declare?

Doctype is not relevant here. Safari shows the same behaviour in both
Quirks and Standard mode, so the same part of the tag soup parser is
handling inline elements continued past a block end.

I did a fairly comprehensive test page, although I didn't test all
inline elements nor all Doctypes.

--
http://www.ericlindsay.com
.

Relevant Pages

  • Re: IE leaks, circular references, addevent et al
    ... Safari due to missing `compatMode` there, ... used in `getContainerElement`. ... What happens if Safari is in quirks mode? ...
    (comp.lang.javascript)
  • Re: doctype nightmare
    ... You don't need to declare any doctype. ... Pages with a complete doctype will be rendered by the browsers in the mode ... In loose or strict rendering mode, ... much as in quirks mode. ...
    (microsoft.public.frontpage.client)
  • Re: IE leaks, circular references, addevent et al
    ... But tested on a variety of clients nevertheless, ... Safari due to missing `compatMode` there, ... What happens if Safari is in quirks mode? ... places it measures the viewport and I'm getting ready to import mine ...
    (comp.lang.javascript)
  • Re: IE leaks, circular references, addevent et al
    ... But tested on a variety of clients nevertheless, ... What happens if Safari is in quirks mode? ... viewport measurement stuff uses a wrapper for getContainerElement. ...
    (comp.lang.javascript)
  • Re: doctype nightmare
    ... >You don't need to declare any doctype. ... >In loose or strict rendering mode, browsers ... >much as in quirks mode. ... >NOT valid HTML. ...
    (microsoft.public.frontpage.client)