-
Notifications
You must be signed in to change notification settings - Fork 4.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
Overlay on disabled elements, to catch events and show tooltips #27529
Overlay on disabled elements, to catch events and show tooltips #27529
Conversation
…d color in order not to paste text with the selection highlight
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Due to this being a change in interaction at a component level I'll also add two apropiate labels.
…d - 1. get default styling (black text) 2. diff the default styling with styles of pasted element to get all nondefault styles applied to element 3. Sanitize output 4. paste the output
I'm not sure if this is caused by the overlay, or an issue with the buttons inherent disabled state (if so feel free to ignore), but I don't think the appearance should change on hover if the button is disabled. |
Nice catch! I have checked it and this behaviour is not connected to an overlay itself. |
In that case I don't think this really needs a design review since nothing has changed visually. |
Allowing disabled buttons to display a tooltip makes a lot of sense to me. |
9a84643
to
589553f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this and looks great. Code lgtm 🥇
Description
Closes #27451
According to the issue #27451 - there was no mechanism for disabled elements to catch events and to display a tooltip.
I have added a layer placed above disabled elements that work as an event catcher and therefore make a tooltip work.
I wouldn't say it is a bug fix, rather a change in current behavior. In my opinion, this change would benefit UX.
How has this been tested?
Unit test added to cover this scenario.
Manual test.
Screenshots
Types of changes
Current behaviour altered
Checklist: