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: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 16 May 2012 20:42:38 -0700
Message-ID: <CAAWBYDD+Lhzxycg1aPzsL22Jb4T8q42kJpEjnX1+08bgDV2W9A@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
On Wed, May 16, 2012 at 7:28 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 5/16/12 4:10 PM, Tab Atkins Jr. wrote:
>> 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?
> <fieldset>?  <applet>?  <progress>?

<fieldset> is display:block already, so it's not troublesome.

<applet> should probably be on the list - I missed it because it only
appears in the obsolete elements list.

Is <progress> (and <meter>) ever a replaced element?

> Should :before and :after content of a flexbox automatically end up as
> flex-items?

No need - they can just be set to display:inline or
display:anything-else as you wish.

> Other than that, this seems ok to me, modulo making the namespace bits clear
> (so <svg:svg> should become a flex-item but <html:svg> probably should not).

Ah, yeah. <html:svg> isn't replaced, as it's an HTMLUnknownElement.

Received on Thursday, 17 May 2012 03:43:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:16 UTC