I had my earlier bug invalidated. I was confused about how the height of table cells is computed. Specifically how non-line boxes push the baseline down.

I'm having a hell of a time trying to make a three column layout where the heights of the three columns match. I've got the basic premise worked out, but what I think are layout bugs in Firefox are screwing everything up. Essentually, any time there is a table in any of the columns, the other columns will have a border the height of that column at the top. So, what I am trying to do is have a layout which uses table-cell as a display, but no table has more than one cell with content in it.

This is the right column. It has jump points for different areas of the site.

Some test content outside of the table.

This is the actual content. It is in a table because I can't keep the retarded CMS from sticking the tags in the output. (And to be fair, I also have some pages that have tabular data.

Blah, blah, here's more after…

This is the right column. It has jump points for different areas of the site.

Some test content outside of the table.

This is the actual content. It is in a table because I can't keep the retarded CMS from sticking the tags in the output. (And to be fair, I also have some pages that have tabular data.

Blah, blah, here's more after…

This is the right column. It has jump points for different areas of the site. Apparently even though it is float it seems to be in the normal flow without any extra trickery. That seems counter to the spec. I reckon I need to test this out in something other than Firefox. Well, it works in Konqueror too.

Some test content outside of the table.

This is the actual content. It is in a table because I can't keep the retarded CMS from sticking the tags in the output. (And to be fair, I also have some pages that have tabular data.

Blah, blah, here's more after…


So, the display is the same in Safari and a bug in Opera makes the side columns disappear completely. What is irritating is Firefox is acting up again. I was doing this to deal with an arguable bug in the table-cell display where there is a nested table. Now, look at what it does with a nested form: (Nothing is changed other than adding the form.)

This is the right column. It has jump points for different areas of the site. A common way to handle jump points is with a form:

Where would you like to go?

Some test content outside of the table.

This is the actual content. It is in a table because I can't keep the retarded CMS from sticking the tags in the output. (And to be fair, I also have some pages that have tabular data.

Blah, blah, here's more after…