Better feedback for when items are disabled
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 146
Description
### Description
Currently, we use the `v-ff-tooltip` directive to add inline tooltips to our buttons and actions. These are great for when the buttons/actions are _active_, but often we disable items for various reasons, but the user is not made aware of _why_ which can be very frustrating.
Take, for example the work done in #3520 - we can see that the first play button is disabled:
But it's not made clear to the user _why_, and given that the button is disabled, the tooltip doesn't show (`pointer-events: none` is being applied)
Fundamentally, we need to establish a better design pattern (and clean up the `v-ff-tooltip` usage across the application) to make sure that users are provided information of the state, as well as still not being able to action things they shouldn't be allowed to.
### Which customers would this be available to
All
### Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Contributor guide
Assessment
This issue has not been assessed yet.