subcolumn equalize

[gauravonnet]

Hi,

The YAML documentation reads

" By assigning the CSS class .equalize, the column containers .cxxl and .cxxr are forced to the same height. The content containers .subcl, .subcr, and .subc do not change "

Does this mean that the two (class .equalize and content containers .subcl, .subc, .subcr) should not be used together. What's the idea behind?
Secondly, in the two equal height example (equal_height_boxes.htm) the heights of the subcolumns have been forced to be equal by use of extra classes (.example1 and .box-top). If an extra class is used to control (and equalize) the height of the subcolumns then what is the use of the factory shipped class ".equalize"?

In a nutshell, I am not able to acheive equal height boxes just by using class .equalize, something that the documentation claims as below

The creation of equal height boxes within YAML is very easy. You activate this property of the subtemplates merely by assigning the surrounding container the additional CSS class equalize.
"
Regards,
Gaurav

[djesse]

Hi,

Does this mean that the two (class .equalize and content containers .subcl, .subc, .subcr) should not be used together. What's the idea behind?

No. The idea of the class .equalize is, that is transforms the floating grid elements into a CSS table where all table columns within a row HAVE equal heights. You can easily test this by adding a background-color or image to these elements. The content containers are child elements of the grid-columns and CAN be forced to have the same height as their equalized parents by adding a big padding-bottom/margin as shown in the provided examles.

http://www.yaml.de/fileadmin/example...ght_boxes.html

Until now the content containers .subcl, .subc, .subcr won't be equalized automatically because these containers are optional and there are use-cases, where an automatically added bottom-padding/-margin would make problems. E.g. think of more than one of such elements within a grid column.

On the other side, there were some mentions of this problem in the past that makes me thinking about a change of this behavior and to automatically force content containers .subcl, .subc, .subcr as well.

In a nutshell, I am not able to acheive equal height boxes just by using class .equalize, something that the documentation claims as below

No, as explained above, the colum-containers will be equalized as they are transformed into a CSS table. But you're right, this could be a bit confusing. A good point to change this in the future.

Dirk

[gauravonnet]

Dirk, Thanks for response.
In respect of your response as below, can you tell how "big" the padding-bottom and margin should be to force the container elements to have the same height as that of their parents? Is there a rule or any arbitrary big value will do?

........ The content containers are child elements of the grid-columns and CAN be forced to have the same height as their equalized parents by adding a big padding-bottom/margin as shown in the provided examles.
http://www.yaml.de/fileadmin/example...ght_boxes.html

Regards,
Gaurav

[gauravonnet]

The above response is not related to the question asked...

[hieblmedia]

Dirk, Thanks for response.
In respect of your response as below, can you tell how "big" the padding-bottom and margin should be to force the container elements to have the same height as that of their parents? Is there a rule or any arbitrary big value will do?


Regards,
Gaurav

Hi,
the minimal value must be the difference between the smallest and the highest container. But the 100em, like in the example, is a good value.