We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug We found that in some places the mouse events don't really make sense.
Examples On the homepage these info-cards grow when you hover on them. This makes them seem clickable, but they're not.
On step 7 of the wizard, the buttons seem clickable because your cursor turns in to a pointer, but they are not clickable here
In wizard step 4 and 5 the box to drop files into is clickable, but your cursor does not turn into a pointer so it's not always clear for the user.
❗ ❗ It could be nice to look over DeX some more and see if the mouseevents in other placers are implemented well, to fix it in other places too.
Expected behavior It should be clear to the user whether an element is clickable or not. If needed, usertest to see if it's clear 😄
Additional context This was found in a usertest that can be found here
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
We found that in some places the mouse events don't really make sense.
Examples
On the homepage these info-cards grow when you hover on them. This makes them seem clickable, but they're not.
On step 7 of the wizard, the buttons seem clickable because your cursor turns in to a pointer, but they are not clickable here
In wizard step 4 and 5 the box to drop files into is clickable, but your cursor does not turn into a pointer so it's not always clear for the user.
❗ ❗ It could be nice to look over DeX some more and see if the mouseevents in other placers are implemented well, to fix it in other places too.
Expected behavior
It should be clear to the user whether an element is clickable or not. If needed, usertest to see if it's clear 😄
Additional context
This was found in a usertest that can be found here
The text was updated successfully, but these errors were encountered: