[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 #19 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(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.

  True: <!DOCTYPE HTML>
        <p><span><div>
           The div gets spit out of the p element
        </div></span></p>

  False: <!--<!DOCTYPE HTML>-->
        <p><span><div>
           The div gets spit out of the p element
        </div></span></p>

  False: <!DOCTYPE HTML>
        <div><span><div>
          The div does *not* get spit out of the p element
        </div></span></div>

  False: <!DOCTYPE HTML>
        <p><object><div>
          The div does *not* get spit out of the p element
        </div></object></p>

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.)

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

Received on Tuesday, 25 February 2014 21:30:23 UTC