diff options
author | patrickhlauke <redux@splintered.co.uk> | 2017-12-26 02:15:21 +0300 |
---|---|---|
committer | Mark Otto <markd.otto@gmail.com> | 2017-12-28 03:28:10 +0300 |
commit | e3f9c463fc862da4d04a1615c0e5aab3df7b2625 (patch) | |
tree | 8aa0e3ef50b7841fa8654d13ba37b34f5b7fc4c7 /scss/_close.scss | |
parent | 8ae78b6820de1489392d21a8c10a65fd93a59533 (diff) |
Opinionated: reintroduce `cursor:pointer`
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 https://github.com/twbs/bootstrap/issues/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`.
Diffstat (limited to 'scss/_close.scss')
-rw-r--r-- | scss/_close.scss | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/scss/_close.scss b/scss/_close.scss index 4271bc720b..f1763cc224 100644 --- a/scss/_close.scss +++ b/scss/_close.scss @@ -12,6 +12,11 @@ text-decoration: none; opacity: .75; } + + // Opinionated: add "hand" cursor to non-disabled .close elements + &:not([disabled]):not(.disabled) { + cursor: pointer; + } } // Additional properties for button version |