Pabini Gabriel-Petit wrote: > I haven't got a great deal of experience when it comes to creating > complex CSS layouts, so please don't assume too much knowledge.
Ok, but it looks like you're trying to hack the livin' daylight out of poor IE... <http://jigsaw.w3.org/css-validator/validator?uri=http://new.uxmatters.com/index.php&warning=1&profile=css21> ...and that's not a good start - especially since most of those hacks are not doing any good in IE or elsewhere. > http://new.uxmatters.com/aboutus/ Styling faulty source-code... <http://validator.w3.org/check?uri=http://new.uxmatters.com/aboutus/> ...also has a tendency to fail... > But on pages generated by Movable Type, I'm getting a float drop when > I make the window narrower than can display the entire page. > http://new.uxmatters.com/index.php ...and the MT source-code looks even worse... <http://validator.w3.org/check?uri=http://new.uxmatters.com/index.php> The problem with all these code-weaknesses is that all browsers will try to "repair" them in different ways, and indeed: your pages turns out differently in every browser on earth and varies wildly even between versions of same browser. No use looking for the cause of one specific failure among all the others in such a case. Better start from scratch and pay attention to web standards while you're at it, and avoid all hacks until you've made it work without any in the good browsers. There's also an enormous amount of unnecessary wrapper-elements in the source-code, of which most seem to be used to create minute offsets in the line-up. Margins on the meaningful elements are better suited for that. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
