Re: [css-flexbox] Flex box does not respect inline children/groupings

On 02/19/2014 01:48 PM, Andrew Fedoniouk wrote:
>> On Tue, Feb 18, 2014 at 6:29 PM, Andrew Fedoniouk
>> <> wrote:
>>> According to this document
>>> (non-normative I believe though) <button> and <input> are
>>> *inline-block* elements. And Eric was asking about purely display:inline
>>> elements that do not generate boxes by themselves.
> I see this:
> button, textarea,
> input, select   { display: inline-block }
> in

So, let's set those elements' display values aside for the moment.

Even if we specifically targeted "display:inline" (not inline-block) and
thereby avoided changing behavior for button/input, we'd still break
<img>, because it's definitely "display:inline" by default, at least in
Firefox/Gecko, Opera/Presto and Chrome/Blink. [the browsers/engines I
have available locally to test]

(From briefly searching, I couldn't find any spec text saying that <img>
should be display:inline by default, but it seems that browsers have
converged on that behavior (probably long ago), and that's not likely to

So the suggested change would still break any existing content that has
<img> as a flex item, even if it wouldn't break <input>/<button>/etc.

> When you apply flexbox on span's container that span gets
> treated as boxed element loosing its display:inline nature.
> Check this,
>   [sample code omitted]
> two divs here should be rendered in the same way.
> That's what Eric was asking about I believe.

Yes, Tab already recognized and responded to that; see his first reply
on this thread:


Received on Wednesday, 19 February 2014 22:15:30 UTC