I'm using Panels 3.0rc1 with Garland and I just try to use Airy Blue. But I found the layout is changed after I switch to Airy Blue. Please check the 2 attachments, in Garland, the width of the internal block is larger than Airy Blue.

I'm not sure is this Airy Blue's problem, maybe it's due to other modules.

CommentFileSizeAuthor
airyblue_panels.jpg62.23 KBdennys
garland_panels.jpg73.26 KBdennys

Comments

geerlingguy’s picture

Assigned: Unassigned » geerlingguy
Category: support » bug

Whoops! I've forgotten to style some table/admin elements for Airy Blue. I'll get to this as soon as I can... please be patient, as I'm trying to finish up a separate project this weekend.

geerlingguy’s picture

For the short term, adding the following CSS rule to pages.css, then rebuilding your cache, should work:

#content-area table {
	width: 100%;
	overflow: scroll;
}
dennys’s picture

Thanks, but it doesn't work. I clear the cache and stop the CSS optimization feature but got the same result.

Test in FF 3.5, Chrome 2.0beta and IE 6.

geerlingguy’s picture

I'll check into this again; do you have a sample page I could test this on? Or if you could copy out the source code for that area of your page, that would be helpful.

dennys’s picture

Sure, this is my page http://dennys.tiger2.net/

But because I just upgrade to PHP 5.3 (I know D6 doesn't support it yet) and some function may error. But it should not impact the test.

geerlingguy’s picture

Ah, okay... you want to add the following rule (I'll wrap this into an update a.s.a.p.) - I didn't see how panels was working, but now I can see where I was wrong above.

#content-inner table {
width: 100%;
overflow: scroll;
}
dennys’s picture

It works, although the alighment is still a little strange, but I think it's ok, thanks.

geerlingguy’s picture

If you'd like all the date columns to be the same width, you can add that in like so:

td.views-field-created {
  width: 100px; /* Insert your own value here */
}
geerlingguy’s picture

Status: Active » Fixed

Wrapping into 6.x-1.2 update (to be posted soon!).

Status: Fixed » Closed (fixed)

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