- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Feb 2014 17:33:46 +0000
- To: www-validator-cvs@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24559 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NEEDSINFO |--- --- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> --- Regarding if I can see a need for the document in question to use border="1", then I think it is positive to use border="1" as this attribute causes borders to be rendered even if you run browser with/in a very simple mode, without CSS. I would not recommend @border on layout tables, but on data tables, I think it is fine. And since table@border=1 is fully permitted by the HTML5 specificaiton, one can just as well ask: Do you see a need to *not* use it? Thus, since, regardless of the need to use border=1, HTML5 permits its use, it is clearly erroneous to issue the message that border=1 is obsolete. Though the issue have been decided by the HTML working group, then, if my opinion is interesting: I disagree with your attitude of creating a dichotomy between using CSS and using native HTML features, such as table@border=1. It is a false dichotomy. When the issue was discussed by the HTMLwg, then, per the understanding of many, the default display for tables *ought to have been* that tables are rendered. However, that train has passed. Instead we got @border=1 as an optional feature. I personally would recommend always using @border=1 and rather use CSS to disable border display when it should not be there. (Unless, of course, we are speaking layout tables.) I think you have enough information to remove the message that claims that the border attribute is obsolete. I reopen the issue. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 7 February 2014 17:33:48 UTC