-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flexbox percentage removed #26
Comments
This also converts {flex: 1 0 0px} to {flex: 1 0 0}, which breaks IE11. |
The problem appears to be fixed in the latest chrome, it doesn't mind about the missing units anymore. |
The commit from @futtta may fix the percentage issue, but it doesn't fix the general units issue. |
do you have example CSS for that @damienmckenna? I'll be happy to improve :-) |
How about something as simple as the following:
|
@futtta, the latest code in your fork appears to resolve this, would you mind putting together a PR of just this fix so we could review it and make it easier to be included? All that's needed are these two bits:
Thanks. |
@damienmckenna; PR #30 created |
@futtta: Excellent, that PR covers it! |
Fixed in v2.4.8-p7 release. Thank you guys! |
{flex: 1 1 0%}
is optimized into{flex:1 1 0}
, which is not rendered the same in Chrome.Cfr. Autoptimize support topic on https://wordpress.org/support/topic/google-chrome-css-flex-1-1-0-is-not-the-same-as-flex1-1-0
frank
The text was updated successfully, but these errors were encountered: