On Nov 10, 2006, at 02:12, fantasai wrote:
Henri Sivonen wrote:
On Oct 27, 2006, at 16:21, Anne van Kesteren wrote:
On Fri, 27 Oct 2006 15:17:16 +0200, Lachlan Hunt
<[EMAIL PROTECTED]> wrote:
That's fine for document conformance, but what about how
browsers will handle it? Is the spec still going to require
browsers to render overlapping cells, or would it be possible to
resolve this difference between HTML and XHTML rendering, as
documented in CSS 2.1 [1]?
http://www.w3.org/mid/[EMAIL PROTECTED]
[1] http://www.w3.org/TR/CSS21/tables.html#q7
WHOA! How on earth did that end up in a CSS WG draft in general
and in the CSS 2.1 draft in particular?
Easy: it didn't get removed.
http://www.w3.org/TR/CSS2/tables.html#q7
I hope that the CSS WG accepts Anne's objection and defines rendering
in a browser-compatible way.
For the table integrity checker I implemented what browsers do: A
cell slides to the right until there's a free slot for its top left
corner. If the cell spans multiple columns and overlaps with a cell
still in effect from an earlier row, it is an error, but doesn't
cause the cell to move further to the right. Since browsers
interoperate, I think it would be a bad idea to change this behavior.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
