[Bug 24591] Make W3C HTML5 spec clearly and correctly state that table@border is obsolete & invalid (nonconforming)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24591

--- Comment #14 from Sam Ruby <rubys@intertwingly.net> ---
(In reply to Leif Halvard Silli from comment #13)
> If we focus on the wide issue:
> 
> When it comes to the wider issue, and thus to other features, such as e.g.
> <center>, block elements as child of <span> and - relevant to table@border -
> table@rules and table@frame, then I believe I am very much on the side of
> making ”presentational” features conforming. However, what would that mean
> in practice? Would it mean to seek to narrow down their use cases and define
> their semantics as ”for this and that use case”? The alternative of
> permitting them without any usage rules, seems out of question to me.

I don't believe that rules should be created in a vacuum.  Instead we should
start with a list of representative and/or high traffic sites and identify what
markup is being intentionally used in ways that don't produce unexpected
results and work to recognize such uses as valid.

<center> may no longer be in vogue, but it still works as advertised.  And
clearly is still being actively used by companies that understand deeply what
the web is and what their use case is.

By contrast, block elements expressed as if they were a child of of a <span>
element don't end up that way in the DOM.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 25 February 2014 17:33:06 UTC