- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Sat, 14 May 2011 21:06:35 -0700
- To: Andrew Fedoniouk <news@terrainformatica.com>
- Cc: Alex Mogilevsky <alexmog@microsoft.com>, David Hyatt <hyatt@apple.com>, www-style@w3.org
On Fri, May 13, 2011 at 9:44 PM, Andrew Fedoniouk <andrew.fedoniouk@live.com> wrote: >> -----Original Message----- From: Tab Atkins Jr. >> 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. Ah, you're right. For some reason I was convinced they were 'inline' for some legacy reason. A quick check, though, shows that they are just 'inline-block'. <img> is still stuck being 'inline', though, and I think we'd still like <img> to "just work" in a flexbox. ~TJ
Received on Sunday, 15 May 2011 04:07:22 UTC