SpaceGirl said:
This caused the problems to appear:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Yep that triggers Standards mode.
This fixes it in IE
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Yep that triggers Quirks mode.
Yep... I knew there were issues, but it wasn't until I hit this obscure
problems (horizontal scrolling) that I had to start digging and work out
"why".
Nothing very obscure about it. According to the specs the scrollbars
of frames (i or otherwise) must either be both on or both off
(scrolling="auto" means that if one is needed both will be shown but
if neither are needed neither will be shown), in Standards mode IE
applies this rule.
I cant show you and URL as both sites I had issue with are under
NDAs. You can check out
www.garbage.com over the next week or so to see the
resulting site.
I'll try to remember, is there a new album out any time soon?
I hope the new site is better than the junk that's there at the moment
which is a fairly perfect example of almost everything that can be
done wrong on a web site.
Couldn't test... dont have access to IE5. I just tell all IE browsers to
render as HTML
All browsers will render it as HTML anyway (I'm guessing on past posts
that you're serving everything as text/html so you're telling all
browsers that it is HTML, regardless of the doctype used).
This is not an XHTML vs HTML issue at all. You would have exactly the
same issues if you used HTML.
You should try to test in IE5 as even in Quirks mode there are
differences between what IE6 does and what IE5 does.
Dont see how it could... same browser will always get the same document, and
my server caches the scripts. The only downside is a small processing hit on
the server when it decides what header to send. But I'm already doing a
process that munges the style sheets because of weirdness on IE/Mac, so I
doubt it's significant.
The page goes out from your server to a proxy. The proxy is used by
many different users, some of whom have IE, some of whom don't. Either
the proxy server caches the page, in which case some users get the
wrong version, or the proxy server always fetches the page from your
server adding extra time to the transaction.
Trying to make my sites as accessible and "standard" as possible.
By serving XHTML under an HTML doctype? I don't think so.
You'd be much more standards compliant if you wrote HTML and served it
with an accurate doctype. It could trigger quirks mode if you needed
it to and you wouldn't need any silly server side hacks.
Doing that already - sadly this particular issue is purely tag related,
rather than CSS. I couldn't fix it in CSS.
That doesn't means that someone else couldn't fix it. ;-)
Whilst there's nothing you can do about the scrollbars (extraneous or
coloured) except avoid frames of all sorts and resist the temptation
to colour them, the "random spaces and gaps, strange positions on some
divs" probably can be fixed by applying a bit of magic to the CSS.
Steve
