W3C home > Mailing lists > Public > www-style@w3.org > February 2016

Re: [css-break] display:contents and break-before/after

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 29 Feb 2016 00:42:29 -0500
To: Francois Remy <frremy@microsoft.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: CSS WG <www-style@w3.org>
Message-ID: <56D3DA45.2020708@inkedblade.net>
On 02/23/2016 11:41 AM, Francois Remy wrote:
>> On 02/19/2016 02:15 PM, Tab Atkins Jr. wrote:
>>> On Fri, Feb 19, 2016 at 10:59 AM, Francois Remy <frremy@microsoft.com>
>> wrote:
>>>> Could we please define in the spec how {    display: contents;
>>>> break-before: abc;    break-after: cde;    } works? Or it is defined and I
>>>> just happened to miss that?
>>>>
>>>> Currently it looks like it works in Firefox.
>>>
>>> Define "works"?
>>>
>>> Anyway, even if the element doesnt' generate a box, it can still
>>> create breakpoints before/after the place where it *would* have been.
>>
>> Exactly what that means would have to be defined. If you 'display: contents'
>> on a child of a grid, and then position its children into various random slots,
>> where in the grid is the break?
>>
>> If we want this behavior, it needs to be explicitly specified what happens.
>> E.g. we could spec that the break gets propagated to its first child/last child.
>
> LGTM

Well, okay, but imho this isn't sufficiently useful to justify
the implementation complexity. A box with 'display: contents'
doesn't actually exit, so unless we define special behavior for
it, no other properties can apply to it.

~fantasai
Received on Monday, 29 February 2016 05:44:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:00 UTC