W3C home > Mailing lists > Public > public-html@w3.org > March 2011

Re: ISSUE-155 table-border: Chairs Solicit Proposals

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 25 Mar 2011 21:53:28 +0100
To: Aryeh Gregor <Simetrical+w3c@gmail.com>
Cc: Sam Ruby <rubys@intertwingly.net>, HTML WG <public-html@w3.org>
Message-ID: <20110325215328590088.aab84014@xn--mlform-iua.no>
Leif Halvard Silli, Fri, 25 Mar 2011 21:41:40 +0100:
> Aryeh Gregor, Fri, 25 Mar 2011 12:57:32 -0400:
>> On Wed, Mar 23, 2011 at 8:22 PM, Leif Halvard Silli wrote:
>>> UPDATE: It turns out that HTML5 requires UAs to treat @border as a
>>> boolean:
>  [...]

> Do you have any view on the pros/cons of changing @border=value into 
> @border=border (AKA a boolean attribute)?
> 
> These are the pros and cons that I see:
> 
>  * Pros: 
>   - more obvious that it is a 'fallback' styling measure
>   - better match of the the defined CSS rules.
>   - help authors to avoid border="\digit", which doesn't
>     affect border width (except on <table> itself) anyway.
>   - simpler to for vendors to understand its effect if it
>     is works as a boolean. (Currently there are some bugs,
>     most prominently in Webkit - see bug report.[1])
>  * Cons: 
>   - some current UAs have bugs which means that they may not 
>     treat <table border="border"> equal to <table border="1">
>     (Most prominently Webkit - see my bug report. [1])
> 
> In my view, the pros outweighs the cons.

PS: the Webkit bug only affects XHTML. 

> [1] https://bugs.webkit.org/show_bug.cgi?id=56982
-- 
leif halvard silli
Received on Friday, 25 March 2011 20:54:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:26 GMT