"Ahem A Rivet's Shot"  wrote

| > Those two statements don't follow. "Render correctly" means show what
| > the valid parts of HTML and CSS state. It does not mean show what the
| > author intended to be shown.
|
| There are no bug free HTML and CSS renderers. Web designers design
| to the bugs of the mainstream browsers.

  Yes. There have been lots of little things in the past,
such as one browser rendering a 1px border on elements
that another browser doesn't. Some of those things are
not so clearcut. It's a system that was designed for
flexibility, displaying on a variety of devices. It wouldn't
be realistic to imagine there's one valid rendering in
all cases. You just have to code it and see how it looks.
I'm amazed browsers can do it at all. It's become
incredibly complex.

    Though in the past I've
found that anything not IE will render complex layout
dependably. I can design for IE quirks mode and all other
browsers, allowing dependable rendering in pretty
much all cases using only two versions of my pages.
But those pages are actually hybrids, also. For example,
some versions of IE can't render a DIV as a block element.
So to work in both IE and Firefox I've had to do things like
nested DIVs and TABLEs. The purists will say that's wrong.
But the purists don't have pages that need to render
correctly. :)

--- SoupGate-Win32 v1.05