2012-01-05 19:01:42 +01:00
|
|
|
.close {
|
|
|
|
|
float: right;
|
2017-01-03 22:51:06 +01:00
|
|
|
font-size: $close-font-size;
|
2014-12-02 23:02:35 +01:00
|
|
|
font-weight: $close-font-weight;
|
2013-04-24 00:41:06 +02:00
|
|
|
line-height: 1;
|
2014-12-02 23:02:35 +01:00
|
|
|
color: $close-color;
|
|
|
|
|
text-shadow: $close-text-shadow;
|
2016-11-26 01:03:13 +01:00
|
|
|
opacity: .5;
|
2013-04-09 19:43:37 +02:00
|
|
|
|
2015-01-01 10:05:01 +01:00
|
|
|
@include hover-focus {
|
2014-12-02 23:02:35 +01:00
|
|
|
color: $close-color;
|
2012-01-05 19:01:42 +01:00
|
|
|
text-decoration: none;
|
2016-11-26 01:03:13 +01:00
|
|
|
opacity: .75;
|
2012-01-05 19:01:42 +01:00
|
|
|
}
|
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`.
2017-12-26 00:15:21 +01:00
|
|
|
|
|
|
|
|
// Opinionated: add "hand" cursor to non-disabled .close elements
|
2018-01-15 21:51:01 +01:00
|
|
|
&:not(:disabled):not(.disabled) {
|
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`.
2017-12-26 00:15:21 +01:00
|
|
|
cursor: pointer;
|
|
|
|
|
}
|
2015-01-20 01:11:39 +01:00
|
|
|
}
|
2012-03-26 05:41:59 +02:00
|
|
|
|
2015-01-20 01:11:39 +01:00
|
|
|
// Additional properties for button version
|
|
|
|
|
// iOS requires the button element instead of an anchor tag.
|
|
|
|
|
// If you want the anchor version, it requires `href="#"`.
|
|
|
|
|
// See https://developer.mozilla.org/en-US/docs/Web/Events/click#Safari_Mobile
|
2016-02-06 21:28:18 +01:00
|
|
|
|
2017-10-03 05:34:56 +02:00
|
|
|
// stylelint-disable property-no-vendor-prefix, selector-no-qualifying-type
|
2015-01-20 01:11:39 +01:00
|
|
|
button.close {
|
|
|
|
|
padding: 0;
|
2017-11-06 01:23:36 +01:00
|
|
|
background-color: transparent;
|
2015-01-20 01:11:39 +01:00
|
|
|
border: 0;
|
|
|
|
|
-webkit-appearance: none;
|
2013-04-23 09:30:22 +02:00
|
|
|
}
|
2017-10-03 05:34:56 +02:00
|
|
|
// stylelint-enable
|
