-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Default hover style not visible on Chrome (Ubuntu 22.04, KDE Neon) #8247
Comments
I can't reproduce the issue in Chrome. Could you share a video? |
No hover styling visible in Chrome:Untitled_.Mar.17.2023.7_56.AM.webmHover styling visible in Firefox:screen-recorder-fri-mar-17-2023-07-59-26.webm |
@flaviendelangle I remember you used Linux. Can you reproduce this issue? |
Can't reproduce it on Ubuntu 22.04 Chrome Gnome |
Thanks for looking into this. I investigated bit further and somehow my Chrome on Desktop Linux is reporting the hover media query to be I seem to be having the same issue as this commentator. However, I am unable to fix this. Please feel free to close this issue. |
In #10039 (comment) I propose a different media query to accommodate mobile phones that return wrong values for these media queries, but looking at #8247 (comment), it won't make much differences. I'm closing, it does look like an issue that should be fixed down the stack, and not in MUI X, e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=441613#c8. Thanks for the report |
Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/w4u5zi?file=/demo.tsx (Example from docs, https://mui.com/x/react-data-grid/)
Current behavior 😯
Here, the default hover style isn't visible in latest Chrome:
But it is visible in Firefox:
Expected behavior 🤔
Default hover style should be visible in Chrome, as it does in Firefox. I can customize the style for
"& .MuiDataGrid-row.Mui-hovered"
viasx
, which then works in Chrome.Context 🔦
No response
Your environment 🌎
npx @mui/envinfo
Order ID or Support key 💳 (optional)
No response
The text was updated successfully, but these errors were encountered: