-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
md-dialog-confirm hides confirm button before hovering in google chrome #2246
Comments
With the latest google chrome update, buttons are not shown in all dialog boxes. .md-button{ or .md-ripple { |
Can it be somehow fixed inside the library itself? |
I have added the fix in this pull request #2254 Till it will not be fixed in the library my workaround is a bad not scoped .md-dialog .md-dialog-actions { |
…code indentation
…code indentation
When using the
md-dialog-confirm
component, the confirm button is invisible until mouse hover. After the hover, button is kept visible.It happens only in Google Chrome latest version.
Steps to reproduce
I entered the official Vue Material website, on the Dialog - Confirms section, try the example. https://vuematerial.io/components/dialog
Which browser?
Latest vue material (vue-material v1.0.0-beta-14)
Latest Google Chrome (84.0.4147.89 64 bits) - The bug didn't reproduce in an earlier version of the browser I had today in the morning.
What is expected?
To see the text in the confirmation button.
What is actually happening?
The button and its text is completely invisible until the mouse is hovered upon it.
Reproduction Link
Official md-dialog-confirm codesandbox: https://codesandbox.io/s/jvw8pv4z85
My workaround solution
I noticed, testing in the Google Chrome console, that if I removed either the
border-radius: 2px
or theoverflow: hidden
lines, the button appears normally. Removing some other css statements made the button appear, but putting them back in didn't make the button invisible again.I made the following workaround on my base css code. I don't know if it's the best option, but it seems very specific to me to not impact other components:
The text was updated successfully, but these errors were encountered: