Skip to content
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

merge beta-2 release #5

Merged
merged 293 commits into from
Oct 20, 2017
Merged

merge beta-2 release #5

merged 293 commits into from
Oct 20, 2017

Conversation

gijsbotje
Copy link
Owner

No description provided.

XhmikosR and others added 30 commits September 26, 2017 17:16
This is so other plugins can use it too.
We can check for browser compatibility on lint time now.
Check `form-control-focus` mixin, variable name is `$input-focus-border-color`
Remove accidental `alt` addition from Bootstrap stack image.
I feel like `auto` is missing from the values here and that it should be there. Although it is mentioned below, only a single use case, whereas in other sections it appears with the option to set the left margin of an element to auto, for example.
Since flex-order was renamed to just order, change the subtitle.
We need to pass different options and this seems cleaner at this point.

In order for docs.min.js to keeps all comments, we don't pass `compress`.
Overriding the focus outline for links within the dropdown menu
causes accessibility issues for keyboard-only users. This
removes the override, reenabling the browser's default focus
outline.
gijsbotje and others added 29 commits October 19, 2017 01:01
* 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
also pushed a hotfix to gh-pages branch
Rationale: the page is not available locally, only on gh-pages, thus leading to a 404 locally.
As the diff shows, this was for a Firefox Android issue that's since been fixed.

Closes #23817.
…tion to the minimum necessary (#24315)

These were using `z-index: 2` to "Place active items above their
siblings for proper border styling". However, using `z-index: 1` is
sufficient for accomplishing that goal.

In input-group, there were also three `z-index: 3` rules for the
hover/focus/active states. I reduced these to `z-index: 2` since they
just needed to be "one more than normal" (i.e. one more than what is now
`z-index: 1` after my changes).

These changes can be verified by viewing the documentation pages for
Button group, Input group, List group, and Pagination before and after
this commit and observing that the active elements are still "above"
their siblings, so their borders look correct.
If the content of the page does not extend the full viewport height, the sidebars were shortened.
@gijsbotje gijsbotje merged commit 1db943c into gijsbotje:v4-dev Oct 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.