-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[UI] Define the right cursor for interface elements #13873
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
[UI] Define the right cursor for interface elements #13873
Conversation
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.
This is a problem from a UX point of view. If there is no explicit reason to disable a default functionality for a website, it shouldn't be done as it introduces potential friction for the end user.
We don't know how a user interacts with the various bits of text on a page. A website is not an app, they might very well have a good reason to copy headings for example.
|
@Mike-Dropsolid Would be good to have your input here as well, in light of priorities and validating the list of UI changes. |
This reverts commit 0c2d2af.
This reverts commit c9014b5.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 5.x #13873 +/- ##
=========================================
Coverage 62.53% 62.53%
Complexity 34362 34362
=========================================
Files 2260 2260
Lines 102762 102762
=========================================
+ Hits 64258 64259 +1
+ Misses 38504 38503 -1 |
d3fede5 to
7cf1be2
Compare
7cf1be2 to
fa2d19d
Compare
fa2d19d to
a95ee7a
Compare
Esthertests
left a comment
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.
having LordRembo concern in mind, this PR is a great UX change. Nice work @andersonjeccel
|
Concerns by Rembrand were addressed, I'll ask him to review again @Esthertests Thanks for testing! |
Yes they were, I checked it also |
|
Warning All Tier 1 PRs need only 1 code review and 1 user testing before able to merge. I'll update accordingly. |
shinde-rahul
left a comment
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.
Code changes LGTM!!!
Description
This PR makes:
The overall idea is to improve the interaction feedback
📋 Steps to test this PR: