Tables are all fun and games until you start cheating (although I can't believe your still using one for layout). When you try to manipulate your rendering by abusing non-existing elements you set yourself up for disaster. In you particular case, why are you colspanning over non-existing columns? Adding to the mix that a browser is well within its' documented rights to ignore the width set for a table-cell if another column has 'more' content you've created a 'house of cards' which in khtml (Safari has this issue too) isn't holding up.
You might get away with it by setting the css property 'table-layout: fixed' on your table. Additionally you might want to set the width of the two columns in px instead of % (The table is a set width, you might as well keep the browser from having to calculate it). Finally I would set all colspan="5" to colspan="2" and remove the other colspans.
Good luck,
Martin
Main Topics
Browse All Topics
by: xberryPosted on 2009-09-15 at 00:43:22ID: 25332621
Yes, here is the complete list of rendering (css-layout) differences with all known engines.
As I take from there, Chrome is using the Webkit enginge:
http://en.wikipedia.org/wi
other browser comparison tables known to me:
http://www.css4you.de/brow
http://en.wikipedia.org/wi