- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Feb 2014 16:32:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24591 --- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> --- To further fuel the editors with reason to dismiss this bug, I cite the following: 1) There was a change proposal to instantitate table@border=1 Where is the new info that Mike provides? 2) This bug is just about theoretical purity. 3) The bug would open a can of worms: - What about type attribute on <ol>? - What about tables for presentational purposes? (”layout tables”). In fact, if we would like to avoid layout tables as much as possible, then should make @border a *required* attribute, since then, authors would have to take extra steps in order to make the borders disappaer. (Making @border required should have no effect on the permission to to use table@role=presentation.) In fact, one could claim that the failure to make @border required is *the opposite* of what Mike claims! Namely, it represents a defacto ”caving in” to those who misuse HTML tables for presentational layout purposes. And in fact, that is exactly my view. As such, I consder Mike’s proposal a fallacy. In conclusion, there logical and reasonable reasons, perfectly in line with the claim that HTML5 has removed presentational markup, to go in the opposite direction of what Mike claims, something I am quite ready to do. And there are practical reasons (think: consensus and compromise) to put the issue to rest. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 10 February 2014 16:32:34 UTC