Trigger Tooltip on disabled elements #479
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could solve it with CSS on the disabled element: pointer-events: none; |
pomfrida
commented
Aug 17, 2020
| disabled element, shown in the example below. This will help trigger | ||
| the mouse events correctly. Unfortunately, this workaround overwrites | ||
| the 'not-allowed' cursor. | ||
| </Typography> |
There was a problem hiding this comment.
Updated the Storybook with a "Disabled element" example, with workaround for Safari browser for the developers to decide what to use.
pomfrida
commented
Aug 17, 2020
| onMouseOver={handleOpen} | ||
| onMouseEnter={handleOpen} | ||
| onPointerEnter={handleOpen} | ||
| onPointerLeave={handleClose} |
There was a problem hiding this comment.
onPointerEnter and onPointerLeave fixed the issue in Chrome.
pomfrida
changed the title
wenche
approved these changes
Aug 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mouse Events on disabled elements are buggy.
This is a known issue on Safari and Chrome browsers. Testing in Firefox gives us the desired outcome.
Trying to find a workaround that goes for all browsers...