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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 16 May 2012 16:10:50 -0700
Message-ID: <CAAWBYDCWMOtPM1HUoo8wdA7nw1xSo3dnj0e3i50vq+eVh4txKw@mail.gmail.com>
To: www-style list <www-style@w3.org>
This issue was discussed at the F2F.  You can skip the next paragraph
if you don't need a refresher on the issue.

The Flexbox spec declares any child of a flexbox that is a block or
inline-block (more or less - I won't get into the details) to be a
flexbox item, while inline elements instead get wrapped into an
anonymous item.  Unfortunately, replaced elements are display:inline,
and may not even be replaced at all in some circumstances (Firefox
renders <img> as a non-replaced inline when the image fails to load).
However, we'd like layout to be consistent and based only on
computed-time or earlier values.

The discussion during the F2F ended with a proposal that we hardcode a
list of replaced elements that should just always become flexbox
items.  I've now made the relevant change to the spec, and the WG just
needs to either OK it or discuss changes.

The list of elements that always become flexbox items is: <img>,
<canvas>, <svg>, <math>, <audio>, <video>, <iframe>, <object>,
<embed>, <input>, <button>, <select>, or <textarea>.

Any issues with this proposal?

~TJ
Received on Wednesday, 16 May 2012 23:11:40 GMT

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