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

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