-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Should Web Chat buttons display the cursor as pointer on buttons? #1767
Comments
After a little bit of research it looks like this may be a debated topic: the pointer is intended for links, not buttons, because links have low affordance. According to this article, buttons should NOT have the pointer because they by nature are more noticeably a clickable object. Your request is also something that Web Chat doesn't have control of: the Adaptive Cards explorer shows that the cursor does not change to the pointer when hovering on Action.Submit. Converse to the original request, this raises the question, should Web Chat buttons display as pointer or the regular cursor? My inclination is to say that we should actually update Web Chat to display the regular cursor because of the following:
@compulim, @cwhitten, @a-b-r-o-w-n, do you have thoughts? @DesignPolice and @mewa1024, if you have feedback please chime in. |
I will defer to MSFT link above- weak affordance of links vs buttons. This quote from Adam Silver I agree with. If we need to look at our button design and if it needs hover states to make it a better button I think that would be a different issue. |
Based off feedback we'll use this item to track the changes of making sure that all Web Chat buttons do not change the pointer to a cursor. |
Clickable elements like buttons, etc. should have a pointer type cursor on mouse hover so that the user gets to know that the element is clickable.
Repro steps:
The text was updated successfully, but these errors were encountered: