| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Co-authored-by: Shohei Yoshida <[email protected]>
Co-authored-by: Martijn Cuppens <[email protected]>
|
|
|
|
|
|
|
|
mixins
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Future-proof disabling of clicks on disabled `btn-link`. Fixes #25639
ensuring consistency between `btn-link` `<button>`s and `<a>`s when disabled.
|
|
|
|
Closes https://github.com/twbs/bootstrap/issues/25316
|
|
|
|
|
|
|
|
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`.
|
|
|
|
`$btn-disabled-opacity` (#24680)
|
|
|
|
https://github.com/isychev/bootstrap into isychev-btn_input_split_variables
|
|
|
|
1. move a couple of them before the more specific ones.
2. change nesting to be under the same parent selector
3. use the ampersand more
|
|
* Update the form focus mixin to use a manual `$enable-shadows` check so we can always ensure a focus state for accessibility and consistency
* - Add new `$input-btn-focus-width` and `$input-btn-focus-color` variables.
- Replace separate `$btn-focus-box-shadow` and `$input-focus-box-shadow`
variables with unified `$input-btn-focus-box-shadow` to match our
combined variables approach elsewhere.
* Put new focus width var to use in buttons mixins
* use new button input-box shadow var
* Add a new mixin for quickly adding linear gradient to components when $enable-gradients is set to true
* use correct var
* fix focus shadows in button mixins
* Add opt-in gradients to alerts, buttons, carousel, custom radios and checkboxes, custom file input, and dropdown items
* Generate .bg-gradient- utilities
* add headings to colors page and document bg-gradient utils
* update the button color for active status, check with yiq as it's done for basic state and hover state
|
|
|
|
|
|
|
|
|
|
button size classes
|
|
Uses some if/else action to ensure there's readable text on hover. Swapped out a hex value to a variable while I was in there.
Fixes #23398, fixes #23351.
|
|
* use a mixin there
* revamp .btn-link to match default and outline variants
* remove unnecessary properties
|
|
When focused, these buttons styled as links still give good visible focus indication through the underline, so this should not be a concern. Closes #22655
|
|
and generate card, button, bg, and color classes from the sass map
|
|
* Rename variable $input-border-focus to $input-border-color-focus
* Rename variables $pagination-hover-border, $pagination-active-border, $pagination-disabled-border to $pagination-hover-border-color, $pagination-active-border-color, $pagination-disabled-border-color, respectively
* Rename variables $state-*-border to $state-*-border-color, respectively
* Rename variables $alert-*-border to $alert-*-border-color
* Rename $list-group-active-border to $list-group-active-border-color
* Rename $table-inverse-border to $table-inverse-border-color
* Rename $btn-*-border to $btn-*-border-color
* Rename $navbar-*-toggler-border to $navbar-*-toggler-border-color
|
|
|
|
|
|
Despite now having the ability to override outline-variant color, it's not actually being used so each are still #fff
Related: https://github.com/twbs/bootstrap/pull/20734
|
|
also be sure to apply it for the active state when shadows are enabled
|
|
shoutout https://medium.com/simple-human/buttons-shouldnt-have-a-hand-cursor-b11e99ca374b#.riy12ck0m
|
|
- removes original outline removal (hah)
- replaces it with an explicit `outline: 0` on `.btn`
- instead of replicating `:hover` for `:focus`, uses custom and themed `box-shadow` for an "outline"
- not mapped to the `$enable-shadows` variable because accessibility
|
|
Trying to simplify our output here by revamping these selectors. We overcomplicated things by setting hover styles for nearly every state (disabled and active included), and we set them in the wrong order.
This commit does the following:
- Reorders states so disabled comes before active, thereby removing the need to set disabled-active styles.
- Removes all focus and hover styles from disabled states as those will naturally inherit from the default button state.
- Renamed `.open` to `.show` to fix dropdown toggle highlighting.
- Tweaked some indendation in the Sass.
|
|
|
|
* Add variables for transitions
* Add variables for transitions
|
|
Websites might use different weights such as medium or thin or use light as default weight instead of normal.
Also referenced: #18605 and #16170.
|
