- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 15 Apr 2011 17:13:09 -0700
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Maciej Stachowiak <mjs@apple.com>, www-archive@w3.org
On Fri, Apr 15, 2011 at 5:00 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Leif Halvard Silli, Fri, 15 Apr 2011 23:35:11 +0200: >> Tab Atkins Jr., Fri, 15 Apr 2011 14:10:15 -0700: > >>>>>> But I believe you agree that it is an error of HTML5's Rendering >>>>>> section to say that border="0" should result in a 1px border. >>>>> >>>>> No, because HTML says nothing of the sort. >>>> >>>> I'm glad that we agree that it shouldn't say such a thing. >>> >>> Perhaps you should read the Rendering section more carefully. It >>> defines <table border=0> such that no border is rendered on the table. >> >> The other option is that you read bug 12413 - including the comments >> there - carefully. >> >> [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12413 > > I'd really like to hear your explanation on this. > > In bug 12413, then Aryeh explicitly (and James implicitly, by not > protesting after I reopened the bug) accepted that they misinterpreted > what HTML5's Rendering section says. > > Until you provide details to the opposite, it seems most logical to > assume that you are under the same misunderstanding that Aryeh and > James once where. Indeed, there is an inconsistency in the current Rendering section, as it applies the rule about mapping @border values to 'border-width' lengths only to the <table>, not the contained cells. ~TJ
Received on Saturday, 16 April 2011 00:13:56 UTC