-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[autoprefixer] Fix a style issue with user agent all and display flex #5668
[autoprefixer] Fix a style issue with user agent all and display flex #5668
Conversation
Thanks @oliviertassinari for accepting my issue. And sorry for late reply. But My app didn't work with this patch (like 👇) because of UA: 'all' universal configuration for SSR caching... hmm... |
@masakij Could you provide more details regarding this issue? |
My app has an universal ThemeProvider like below. const muiTheme = getMuiTheme(baseTheme, { userAgent: 'all' });
class App extends React.Component {
render() {
return (
<MuiThemeProvider muiTheme={muiTheme}>
{children}
</MuiThemeProvider>
);
}
} This provider is used by server & client. <Avatar>A</Avatar> ⬇️ <div size="40"
style="
color:#ffffff;background-color:rgb(188, 188, 188);
user-select:none;
display:-webkit-box,-moz-box,-ms-inline-flexbox,-webkit-inline-flex,inline-flex;
align-items:center;
justify-content:center;
font-size:20px;
border-radius:50%;
height:40px;
width:40px;
mui-prepared:;
-webkit-user-select:none;
-moz-user-select:none;
-ms-user-select:none;
-webkit-align-items:center;
-webkit-justify-content:center;
-ms-flex-align:center;
-webkit-box-align:center;
-ms-flex-pack:center;
-webkit-box-pack:center;
"
data-reactid="7">
<!-- react-text: 8 -->A<!-- /react-text -->
</div> Rendered element's display value is broken. I tried another way specifing userAgent. It works, but get invalid checksum warning. Thanks |
That's expected, I have linked this issue facebook/react#6467 in the first PR. You can't prefix for all user-agent on the client. The server-side rendering with
IMHO, that's totally fine. There is an issue on the React repository regarding that point.
You can have a look at the |
I tested just in case
hmm... It's not good. I'd like to make sure that SSR is not ignored.
It's sounds good. I'll check it. |
Is there any solution? I have the same issue |
This is a continuation of #5648.
Thanks @masakij for raising this issue
Fix #5648.