- From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
- Date: Fri, 13 May 2011 21:44:27 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "Alex Mogilevsky" <alexmog@microsoft.com>, "David Hyatt" <hyatt@apple.com>, <www-style@w3.org>
>-----Original Message----- >From: Tab Atkins Jr. >Sent: Friday, May 13, 2011 9:18 PM >To: Andrew Fedoniouk >Cc: Alex Mogilevsky ; David Hyatt ; www-style@w3.org >Subject: Re: [css3-flexbox][css3-grid] Inline replaced elements as grid >items and flexbox items > >On Fri, May 13, 2011 at 7:33 PM, Andrew Fedoniouk ><andrew.fedoniouk@live.com> wrote: >>> -----Original Message----- From: Alex Mogilevsky >>> So that is the reasoning that brought us to accepting replaced inline >>> blocks as flexbox items. We initially suggested that any inline blocks >>> should work, what we have is a compromise, but if we wean to revisit the >>> decision I would again suggest that inline blocks are included for >>> consistency... >>> >> >> As <button>,<img>,<textarea>,etc. are display:inline-block >> elements then how about these rules: >> >> 1. To treat all display:block, table, inline-block, list-item elements as >> flex boxes. display:inline and text content will be wrapped into >> boxes. > >They're display:inline, for legacy reasons that can't be changed now. >If they were 'inline-block' we wouldn't be having this discussion, as >the answer would obviously be exactly what you just said. > If button would be display:inline then this element: <button>multiple words here</button> will wrap on multiple lines in no space condition. I haven’t seen any UA that does this, have you? Actually it is quite opposite: all UAs in the wild are forcing <button>, <input> and others to be display:inline-block. No matter what is defined for them in CSS. If it is not so then could you elaborate more on those "legacy reasons"? Name of the UA that allows <button> to be display:inline would be also interesting to know. -- Andrew Fedoniouk http://terrainformatica.com
Received on Saturday, 14 May 2011 04:44:59 UTC