And what does the contentpane class look like in the CSS?  What does the rendered HTML have?  What did Firebug or any number of web developer toolbars show?

Jeff

If you use the <td></td> method for placing content panes in the skin, anything placed between the tags will appear before your content when the page is rendered, so it's best to not put anything between the td's for content panes.  Not sure if that applies to other methods as well or not.

If a content pane has padding applied in the css and it's an empty pane (no content), DNN will NOT fully collapse it; the padding will remain visible.   I haven't tried to remove it using the dnnemptypane class in the skin css files, but that would be one approach.  What I do is set all margins and padding for content panes to zero and apply left and right padding to the containers instead, and since ie has the box model problem, I usually use spacer.gif's for padding instead of the actual css padding.  I don't like to use css hacks because eventually they will become obsolete or not work with new releases, etc.  Anyway, by setting the padding and margins to zero for the content panes in the skin.css file, there is no chance for any browser to have difficulty rendering a collapsed content pane without padding.  Either of those two approaches should help line up your left aligned containers on the home page.

I don't see a difference in the placement of the modules or their content between ie7 and ff3, but ie7 definitely renders the page about 50% wider than ff3, and I'm not sure what to recommend there except checking your skin or possible inline styles for width or padding or maybe even font size settings that are causing ie to render the page substantially wider.

Hope that helps,

Rick

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke