You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
Bug 12, "Inline elements are not treated as flex-items", seems to be
misdescribed, at least for IE11. With that browser, on Windows 7, if I open
up the workaround (12.1.b, at http://codepen.io/philipwalton/pen/NqLoNp) and
change display: block to display: inline, the bug doesn't strike and the
page is unchanged.
If I reload the page and add
.FlexContainer::before
{
display: inline;
}
at the end of the CSS, the bug doesn't strike and the page is unchanged.
The text was updated successfully, but these errors were encountered:
Hmmm, it looks like you're right. It seems pseudo-elements don't work when no display value is used, but when a display value of inline is used, they work fine. That makes me wonder what default value IE11 gives them.
Unfortunately I don't think it's possible to tell, since the developer tools don't let me select the pseudo-element.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug 12, "Inline elements are not treated as flex-items", seems to be
misdescribed, at least for IE11. With that browser, on Windows 7, if I open
up the workaround (12.1.b, at http://codepen.io/philipwalton/pen/NqLoNp) and
change
display: block
todisplay: inline
, the bug doesn't strike and thepage is unchanged.
If I reload the page and add
at the end of the CSS, the bug doesn't strike and the page is unchanged.
The text was updated successfully, but these errors were encountered: