W3C home > Mailing lists > Public > www-style@w3.org > May 2012

Re: [css3-flexbox] Fixing the "replaced elements may or may not be inline" issue

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 16 May 2012 19:41:21 -0700
Message-ID: <4FB46551.2000306@inkedblade.net>
To: www-style@w3.org
On 05/16/2012 07:25 PM, Boris Zbarsky wrote:
> On 5/16/12 7:22 PM, Boris Zbarsky wrote:
>> On 5/16/12 5:01 PM, fantasai wrote:
>>> I think it's okay.
>>>
>>> An alternative would be to define a 'flex-item' value for 'display',
>>> and make it compute to 'inline' except on children of a flex container.
>>
>> For what it's worth, this would be very hard to implement in at least
>> Gecko without disabling various style-sharing optimizations and hence
>> significant performance and memory use penalties....
>
> Actually, scratch that. I just wasn't thinking straight.
>
> I still think it's a bit weird, but I'd need to think a bit more to
> figure out whether it really is or whether it's just me. ;)

I think it *is* weird. But so's putting a list of special-cased HTML
elements into a CSS spec. So the question is, what's likely to cause
fewer problems down the line?

~fantasai
Received on Thursday, 17 May 2012 02:41:51 GMT

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