Hello!
First, I would like to thank developers who's been working on the Panels2 project. Cool new features and flexibility makes this module work for me.

I have been testing Panels v5.x2.0-alpha11 on Drupal 5.3 and noticed some inconsistencies in the layout of the contents under IE6 vs Safari or Firefox.

When I create any Two column layouts and add a single node on each side of the panel (left & right), depending on the size of the IE6 window the nodes might be displayed in a two columns layout or one. So, if I play around with the window size adjustment and drag it to a half the screen (being my resolution is 1440x900), the page breaks. This behavior does NOT appear to exist under Firefox 2.0.0.7 or Safari 2.0.4

What I would also mention is that even with Three Panel layout, the third node keeps jumping between third column and first with a very slight window movements.

Has anyone seen this type of behavior or might be aware how to fix it? I am not a fan of IE but unfortunately a good 50% of site users are using it

Thanks,

Comments

attiks’s picture

attiks commented

things to check:
- margins and paddings on each of the panels
- if total width is a 100% you can get this, better to set each column to 49% or the total width to 99%

merlinofchaos’s picture

merlinofchaos commented

Indeed, the easiest way to address this is to override the CSS and make the columns a little narrower. Generally what happens is that IE miscalculates (or, if you will, calculates differently than any other browser) the total widths by not including margins in the percentages (or is it padding? I forget.)

THe proper fix is to try and determine all of the margins and padding that make it up, and remove them. This is especially true of the content area itself; somtimes this can be alleviated by adding an extra div with no margin or padding inside the content area.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

Added to the known issues file.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.