Why can't fieldset be flex containers?
According to Bug 984869 - display: flex
doesn't work for button elements,
<button>
is not implementable (by browsers) in pure CSS, so they are a
bit of a black box, from the perspective of CSS. This means that they
don't necessarily react in the same way that e.g. a<div>
would.This isn't specific to flexbox -- e.g. we don't render scrollbars if
you putoverflow:scroll
on a button, and we don't render it as a
table if you putdisplay:table
on it.Stepping back even further, this isn't specific to
<button>
. Consider
<fieldset>
andwhich also have special rendering behavior:<table>
data:text/html,<fieldset style="display:flex"><div>abc</div><div>def</div>
In these cases, Chrome agrees with us and disregards the
flex
display mode. (as revealed by the fact that "abc" and "def" end up
being stacked vertically). The fact that they happen to do what you're
expecting on<button style="display:flex">
is likely just due to an
implementation detail.In Gecko's button implementation, we hardcode
<button>
(and
<fieldset>
,and) as having a specific frame class (and hence,<table>
a specific way of laying out the child elements), regardless of the
display
property.If you want to reliably have the children reliably arranged in a
particular layout mode in a cross-browser fashion, your best bet is to
use a wrapper-div inside the button, just as you would need to inside
ofaa<table>
or<fieldset>
.
Therefore, that bug was marked as "resolved invalid".
There is also Bug 1047590 - display: flex;
doesn't work in <fieldset>
, currently "unconfirmed".
Good news: Firefox 46+ implements Flexbox for <fieldset>
. See bug 1230207.
Fieldset cannot apply flex direction
Fieldset, legends and some other elements can not use flexbox
properly. Its a bug.
A possible Solution can be using <div role="group">
in HTML, and add CSS div[role='group']
as selector.
span { background: lightgreen;}span:nth-of-type(odd) { background: pink;}
div, div[role='group']{ display: flex; flex-flow: row wrap;}
<div role="group"> <span>text 1</span> <span>text 2</span> <span>text 3</span></div>
<div> <span>text 1</span> <span>text 2</span> <span>text 3</span></div>
Why fieldset inside flex act differently between browsers
On Chrome the <fieldset>
is given a min-width
equal to the width of the content. You can remove this by putting in min-width: 0px;
in the <fieldset>
style.
http://jsfiddle.net/wpe03rs6/2/
Flex / Grid layouts not working on button or fieldset elements
The Problem
In some browsers the <button>
element doesn't accept changes to its display
value, beyond switching between block
and inline-block
. This means that a <button>
element cannot be a flex or grid container, or a <table>
, either.
In addition to <button>
elements, you may find this constraint applying to <fieldset>
and <legend>
elements, as well.
See the bug reports below for more details.
Note: Although they cannot be flex containers, <button>
elements can be flex items.
The Solution
There is a simple and easy cross-browser workaround to this problem:
Wrap the content of the button
in a span
, and make the span
the flex container.
Adjusted HTML (wrapped button
content in a span
)
<div>
<button>
<span><!-- using a div also works but is not valid HTML -->
<span>Test</span>
<span>Test</span>
</span>
</button>
<p>
<span>Test</span>
<span>Test</span>
</p>
</div>
Adjusted CSS (targeted span
)
button > span, p {
display: flex;
flex-direction: row;
justify-content: center;
}
Revised Demo
References / Bug Reports
Flexbox on a <button>
blockifies the contents but doesn't establish a flex formatting context
User (Oriol Brufau): The children of the
<button>
are blockified, as dictates the flexbox spec. However, the<button>
seems to establish a block formatting context instead of a flex one.User (Daniel Holbert): That is effectively what the HTML spec requires. Several HTML container-elements are "special" and effectively ignore their CSS
display
value in Gecko [aside from whether it's inline-level vs. block-level].<button>
is one of these.<fieldset>
&<legend>
are as well.
Add support for display:flex/grid and columnset layout inside <button>
elements
User (Daniel Holbert):
<button>
is not implementable (by browsers) in pure CSS, so they are a bit of a black box, from the perspective of CSS. This means that
they don't necessarily react in the same way that e.g. a<div>
would.This isn't specific to flexbox -- e.g. we don't render scrollbars if you put
overflow:scroll
on a button, and we don't render it as a
table if you putdisplay:table
on it.Stepping back even further, this isn't specific to
<button>
. Consider<fieldset>
and<table>
which also have special rendering
behavior.And old-timey HTML elements like
<button>
and<table>
and<fieldset>
simply do not support customdisplay
values, other than
for the purposes of answering the very high-level question of "is this
element block-level or inline-level", for flowing other content around
the element.
Also see:
- Flexbug #9: Some HTML elements can't be flex containers
- 10. Some HTML elements can't be grid containers
Related Topics
Open Link in New Tab or Window
Draw on Html5 Canvas Using a Mouse
Using HTML and Local Images Within Uiwebview
Make Absolute Positioned Div Expand Parent Div Height
How to Draw Vertical Text With CSS Cross-Browser
How to Change or Remove Html5 Form Validation Default Error Messages
How to Specify Line Breaks in a Multi-Line Flexbox Layout
Positions Fixed Doesn't Work When Using -Webkit-Transform
How to Customize ≪Input Type="File"≫
How to Encode/Decode HTML Entities in Ruby
Invert CSS Font-Color Depending on Background-Color
How to Make Blinking/Flashing Text With CSS 3
Css - How to Style a Selected Radio Buttons Label
How Do Search Engines Deal With Angularjs Applications
How to Create a Template in Html
Is It Wrong to Change a Block Element to Inline With CSS If It Contains Another Block Element