All of my zones and regions use a 12 column grid. However, when creating a panel I have the option to use layouts from 16 and 24column gride also. However these don't function correctly as none of the CSS for these layouts has actually been included on the page. Currently, the only way to get it working is to set at least one zone or region to use those column specifications in the theme settings.

Ideally, these additional css grid layouts should be loaded on the fly as and when required by panels, enabling you to use a 16 column panel layout, even though non of your core theme zones or regions actually use this type of layout.

Comments

mrfelton’s picture

mrfelton commented

Also, to add to this. Even if you set one of your regions to use another grid specification in order to get it loaded onto the page, it still doesn't work properly as the container elements in the panels layouts don't contain the container-x classes. So for example, my main content region is a 12 column grid. I set the footer region to be a 16 column grid in order to make those styles available as mentioned in the original bug report. Then, I created a 16 column panel node, but nowehere in the css parent hierarchy does the container-16 class appear, so the css thats applied to my grid-x classes in the 16 column panel are taken from the 12 column grid, which is wrong.

Panels layout templates are going to need the container-x classes included in order to allow embedding of different grid specifications within each other.

cellar door’s picture

cellar door commented
Status: Active » Closed (works as designed)
mrfelton’s picture

mrfelton commented
Status: Closed (works as designed) » Active

How is what 'works as designed'? Surely this is a design flaw.

cellar door’s picture

cellar door commented

My bad - I must have gotten this crossed with another issue as I was cleaning out old non bug reports.

In trying to understand what is going on - your content zone is 12 columns but you want to use a 16 column grid class inside it? I don't use panels so I'm missing how /why you would mix grids like this and not just use 16 columns in the region you're using that panel in.

My only fear is that this may be a larger change the structure of the grid that may effect other aspects of non-panel usage for what seems to be a non-typical use. Again I'm not a panels user so if this is indeed a regular use case we could look into it but with 4.x the grid system is going to be doing a major overhaul so it may be worth it to leave this to include there.