Hi Martin.
yui-g, yui-u, and first combinations are very problematic with content that may not render:
This is what happens: https://devpad.canonical.com/~curtis/yui-columns/firefox-3.0-missing-rows.png
So explored a simple two column approach where the guaranteed portlets are first: https://devpad.canonical.com/~curtis/yui-columns/firefox-one-yui-g-best.png
But this can still look bad in the extreme cases. https://devpad.canonical.com/~curtis/yui-columns/firefox-one-yui-g-worst.png
So I tried this, two columns on guaranteed, a page width of optional, then two columns of optional https://devpad.canonical.com/~curtis/yui-columns/firefox-two-yui-g.png
My last effort does require a lot more thinking on the part of the engineer. the middle fix is actually the easiest implementation we can take with migrate to 3.0
Hi Martin.
yui-g, yui-u, and first combinations are very problematic with content that may not render:
This is what happens: /devpad. canonical. com/~curtis/ yui-columns/ firefox- 3.0-missing- rows.png
https:/
So explored a simple two column approach where the guaranteed portlets are first: /devpad. canonical. com/~curtis/ yui-columns/ firefox- one-yui- g-best. png
https:/
But this can still look bad in the extreme cases. /devpad. canonical. com/~curtis/ yui-columns/ firefox- one-yui- g-worst. png
https:/
So I tried this, two columns on guaranteed, a page width of optional, then two columns of optional /devpad. canonical. com/~curtis/ yui-columns/ firefox- two-yui- g.png
https:/
My last effort does require a lot more thinking on the part of the engineer. the middle fix is actually the easiest implementation we can take with migrate to 3.0