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

Re: collapsible property

From: Ojan Vafai <ojan@chromium.org>
Date: Wed, 10 Feb 2010 17:09:59 -0800
Message-ID: <78dc8441002101709x486ee0fatba7850fbe03dc03b@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org, Daniel Danilatos <danilatos@google.com>, Julie Parent <jparent@chromium.org>
On Wed, Feb 10, 2010 at 5:05 PM, fantasai <fantasai.lists@inkedblade.net>wrote:

> On 02/10/2010 04:36 PM, Ojan Vafai wrote:
>
>> Collapsed block nodes make little sense when dealing with rich-text
>> user-generated content. Rich-text libraries need to go through all sorts
>> of contortions right now in performance sensitive code to get around
>> this. Browser's themselves do things to avoid collapsing nodes (e.g.
>> putting magic BRs in empty block elements). These workarounds are costly
>> and don't always work.
>>
>> Proposal: Add a collapsible property. Defaults to "auto".
>> auto: the current behavior of collapsing block elements when they are
>> empty
>> never: empty elements don't collapse.
>>
>> p {
>>   collapsible: never;
>> }
>>
>
> Are you referring to margin collapsing or to something else?
>

No. I'm referring to empty block nodes collapsing. For example, <p></p> will
render a 0-height paragraph element.

Ojan
Received on Thursday, 11 February 2010 01:10:51 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:24 GMT