Comments on: Internet Explorer Print and CSS http://resource.reh3.com/internet-explorer-print-and-css/ Web design news and notes Thu, 20 Aug 2009 23:39:11 -0700 hourly 1 http://wordpress.org/?v=3.0 By: Jason http://resource.reh3.com/internet-explorer-print-and-css/comment-page-1/#comment-61143 Jason Fri, 15 May 2009 15:19:17 +0000 http://resourcetest.reh3.com/?p=19#comment-61143 I ran into this recently too and thank god I found this article. I had a similar problem with "float: left;" style. Here is my before and after css. Did not print: #MainSection { height: auto; } #LeftSection { clear: left; float: left; min-height: 460px; width: 180px; } Did print: #LeftSection { clear: left; float: left; min-height: 460px; width: 180px; } #MainSection { height: auto; float: left; } I ran into this recently too and thank god I found this article.

I had a similar problem with “float: left;” style. Here is my before and after css.

Did not print:

#MainSection { height: auto; }
#LeftSection { clear: left; float: left; min-height: 460px; width: 180px; }

Did print:

#LeftSection { clear: left; float: left; min-height: 460px; width: 180px; }
#MainSection { height: auto; float: left; }

]]> By: Michael Lennox http://resource.reh3.com/internet-explorer-print-and-css/comment-page-1/#comment-57691 Michael Lennox Thu, 24 Jul 2008 23:11:59 +0000 http://resourcetest.reh3.com/?p=19#comment-57691 I know this is OLD, but we ran into the exact same problem today. In our case, it was also a float:left, but the name was also important. In our case, id="content" which referenced a float:left blew up IE, but only when printing landscape. Thanks for your post. It provided a helpful clue in working to figure out the cause of the problem. The issue was easy to resolve once identified, but it took a while to track it down. I know this is OLD, but we ran into the exact same problem today. In our case, it was also a float:left, but the name was also important. In our case, id=”content” which referenced a float:left blew up IE, but only when printing landscape.

Thanks for your post. It provided a helpful clue in working to figure out the cause of the problem. The issue was easy to resolve once identified, but it took a while to track it down.

]]>