W3C home > Mailing lists > Public > www-style@w3.org > May 2009

RE: "Re: [CSS21] rules="all" attribute specification and border-collapse property"

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 4 May 2009 14:49:49 -0700
To: fantasai <fantasai.lists@inkedblade.net>
CC: Patrick Garies <pgaries@fastmail.us>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <DBCD4020258D924A9887739500CF8E599B77F02A05@NA-EXMSG-C125.redmond.corp.microsoft.com>
> As for expected results, I think the current state of affairs is to
> look at
> the relevant specs and apply some common sense to tie them together. In
> this
> case, my common sense says table { border-collapse: separate }
> shouldn't cause
> cell borders to disappear from a [rules=all] table.
Yes, I got that. However, given that border-collapse's initial value *is* separate then setting rules="all" on a table with no other style rule should not cause any of these borders to vanish either; yet that is what we see in the simplest case across IE8, Firefox and Opera. So if Patrick is correct i.e. IE7 and WebKit do it right, then three browsers have a bug to fix in this case. At the very least, I'd like to understand how our collective common senses all failed in the same way in this simple cas; given what has been said here, I don't understand why *that* rendering is logical or desirable. 

But all this really makes me want to go through all the border-collapse/rules cases, not just this one, so the story is complete. I can't yet offer an ETA though.

Received on Monday, 4 May 2009 21:50:32 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:18 GMT