Opinionated: reintroduce cursor:pointer#25082
Merged
mdo merged 1 commit intotwbs:v4-devfrom Dec 28, 2017
patrickhlauke:v4-dev-reintroduce-cursor-pointer
Merged
Opinionated: reintroduce cursor:pointer#25082mdo merged 1 commit intotwbs:v4-devfrom patrickhlauke:v4-dev-reintroduce-cursor-pointer
cursor:pointer#25082mdo merged 1 commit intotwbs:v4-devfrom
patrickhlauke:v4-dev-reintroduce-cursor-pointer
Conversation
Explicitly re-adds the "hand" `cursor:pointer` for non-disabled `.btn`, `.close`, `.navbar-toggler` elements, as well as forcing `page-link` pagination controls to always have the "hand" cursor (even if an author uses it on, say, `<button>` elements for a dynamically updating in-page pagination). Controversial, as everybody jumped on the bandwagon following this article https://medium.com/simple-human/buttons-shouldnt-have-a-hand-cursor-b11e99ca374b - which does have its merits of course, but there are also counter-arguments like http://kizu.ru/en/issues/cursor-pointer/ And seeing the amount of issues we've seen following the change, and the potential complexity needed to consistently address the cursor issue (see #24156 where i explore how the cursor needs to be based on "intent", and how that's tough to determine), I'm favouring an opinionated take here of just reintroducing the `cursor:pointer`.
Member
|
Please fix the linting issues. Other than that, I'm personally in favor of this, mostly because I'm used to it. |
Member
Author
|
Yeah, linting issue slipped me by. Fixed now :) |
mdo
approved these changes
Dec 28, 2017
This was referenced Dec 28, 2017
Closed
Member
Author
|
cheers boss @mdo |
|
In Bootsrap 4.1 still doesn't work? Any change? |
Closed
2 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Explicitly re-adds the "hand"
cursor:pointerfor non-disabled.btn,.close,.navbar-togglerelements, as well as forcingpage-linkpagination controls to always have the "hand" cursor (even if an author uses it on, say,<button>elements for a dynamically updating in-page pagination).Controversial, as everybody jumped on the bandwagon following this article https://medium.com/simple-human/buttons-shouldnt-have-a-hand-cursor-b11e99ca374b - which does have its merits of course, but there are also counter-arguments like http://kizu.ru/en/issues/cursor-pointer/
And seeing the amount of issues we've seen following the change, and the potential complexity needed to consistently address the cursor issue (see #24156 where i explore how the cursor needs to be based on "intent", and how that's tough to determine), I'm favouring an opinionated take here of just reintroducing the
cursor:pointer.Closes #24954, closes #24156, and closes #23224.