24641 2014-02-13 00:56:43 +0000 Consider making border a boolean attribute 2014-02-28 16:29:01 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED WONTFIX http://www.w3.org/html/wg/drafts/html/master/tabular-data.html#the-table-element P2 normal --- 24636 1 xn--mlform-iua dave.null mike public-html-admin public-html-wg-issue-tracking robin xn--mlform-iua public-html-bugzilla oldest_to_newest 100457 0 xn--mlform-iua 2014-02-13 00:56:43 +0000 Because all of the following variants of table@border cause table cells to be rendered with 1px borders, it would be simpler to authors if the element became a boolean attribute. border="" border="1" border="not-a-number" The rendering rules did not have to change. Only the authoring rules. To avoid useless error messages, border=1 could perhaps be made ”obsolete but conforming”. Thus, consequently, border="" and border="border" would become the conforming values. The following regime, were border=1 is fully conforming, might be interpreted by authors as if border= can take any number as value. Whereas in reality, border is just a on-off signal. 100494 1 robin 2014-02-13 11:06:01 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: As per bug 24591 we are moving towards making border non-conforming. There is absolutely no value in making border a boolean attribute given that its only use is presentational. Using border as an indicator that a table is not presentational is not a sensible heuristic for the specification: that's the default value anyway. 100515 2 xn--mlform-iua 2014-02-13 12:28:54 +0000 (In reply to Robin Berjon from comment #1) > Status: Rejected > Change Description: none > Rationale: As per bug 24591 we are moving towards making border > non-conforming. There is absolutely no value in making border a boolean > attribute given that its only use is presentational. Using border as an > indicator that a table is not presentational is not a sensible heuristic for > the specification: that's the default value anyway. As per the my comments in bug 24591, including reference to a HTML WG decision, it does not make sense to keep border out of the list of permitted attributes. 101630 3 robin 2014-02-28 16:29:01 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: If it is a genuinely a good idea to use the @border attribute to indicate that a table is non-presentational, since the expectation is that table should never be presentational, then the only logical choice would be to make table elements that do not feature the @border attribute non-conforming. Arguing for a heuristic based on what is de facto an obsolete feature is one thing; changing said heuristic is another. Authors who wish to flag their non-presentational table as non-presentational are already wasting 10 characters; it does not seem particularly useful to help them save 3 of those.