[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 #20 from Sam Ruby <rubys@intertwingly.net> ---
(In reply to Leif Halvard Silli from comment #19)
> (In reply to Sam Ruby from comment #14)
> > (In reply to Leif Halvard Silli from comment #13)
> > > If we focus on the wide issue:
> 
> > 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.
> 
> Not so fast. That is true *only* when <p> is not the parent *and* the page
> is *not* in quirks-mode.
> 
>   [snip]
> 
> So, basically, it is only for <p> that what you say about ”block being spit
> out of span in the DOM” is (mostly) true. In fact, I remember Hixie
> providing the tip sometime that one could wrap block element sin span ... 
> (Must have been in 2007.)

Fair enough.  While that changes my specific recommendation, that actually
strengthens my overall recommendation, namely that if people are en-mass
ignoring restrictions in the specification, but are doing so in ways that are
effective and interoperable, then the restrictions should be lifted.  To do
otherwise reduces the utility of both the specification and any validators
based on the specification.

See also:  http://www.w3.org/TR/html-design-principles/ (specifically: Support
Existing Content, Pave the Cowpaths, and Priority of Constituencies).

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

Received on Tuesday, 25 February 2014 22:17:32 UTC