On Tue, Sep 20, 2016 at 1:15 AM, Simon Pieters wrote:
> On Tue, 20 Sep 2016 02:54:56 +0200, Boris Zbarsky wrote:
>> On 9/20/16 1:46 AM, Mats Palmgren wrote:
>>>
>>> Assuming that the above are the final DOM trees, then they should
>>> create exactly the same CSS boxes as if the element is replac
On Tue, 20 Sep 2016 02:54:56 +0200, Boris Zbarsky wrote:
On 9/20/16 1:46 AM, Mats Palmgren wrote:
Assuming that the above are the final DOM trees, then they should
create exactly the same CSS boxes as if the element is replaced
by its (DOM) children.
That contradicts what fantasai claimed t
On 9/20/16 2:44 AM, Mats Palmgren wrote:
Which is pretty much what I said above, no?
That depends on whether the requirements around summary and legend in
the HTML spec are "box generation and layout" or not, right?
-Boris
On 09/20/2016 02:54 AM, Boris Zbarsky wrote:
On 9/20/16 1:46 AM, Mats Palmgren wrote:
Assuming that the above are the final DOM trees, then they should
create exactly the same CSS boxes as if the element is replaced
by its (DOM) children.
That contradicts what fantasai claimed the spec says.
On 9/20/16 1:46 AM, Mats Palmgren wrote:
Assuming that the above are the final DOM trees, then they should
create exactly the same CSS boxes as if the element is replaced
by its (DOM) children.
That contradicts what fantasai claimed the spec says.
Which brings me back to my claim that the spe
On 09/20/2016 12:53 AM, fantasai wrote:
legend
and what about:
details
Text.
Assuming that the above are the final DOM trees, then they should
create exactly the same CSS boxes as if the element is replaced
by its (DOM) children. (The only d
