| Age | Commit message (Collapse) | Author |
|---|
|
justify-content:between ⇒ justify-content:space-between
|
|
|
|
Fix typo
|
|
|
|
|
|
v4-dev is using Jekyll, not Hugo.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Stack in cards in one column when < md
|
|
|
|
|
|
- Rename and move the variable to variables file
- Move code to the grid file
- Use the mixin to generate our own classes
- Wrap in a grid classes enabled conditional
- Document the mixin
|
|
|
|
Trying to find a new way to do responsive card decks while not locking ourselves into the cards themselves. My thinking here is we can easily control the column (.col) width by the parent, but I don't know how many we need (have 0-5 now) across each breakpoint. This works for cards so far, and I think could get us equal height, too.
|
|
The example shortcode already adds this.
|
|
Use the built-in utilities instead.
|
|
Also, add a warning in _root.scss so that we don't miss it again.
|
|
|
|
|
|
|
|
allow to pass popper.js configuration for tooltip/popover and dropdown
|
|
|
|
|
|
* Follow-up to #29095
This PR fixes the responsive containers that were added in #29095, originally stubbed out in #25631. Apologies to @browner12 for getting that wrong.
Fixes #25631.
* update navbar as well because we cannot reset all containers uniformly
* Update navbars example to include container-xl example to ensure containers match
* rewrite responsive containers docs, add table of max-widths
* Update container docs
- Move table up to the intro
- Remove the container example because it's actually hella confusing
- Update and link to grid example as a demo instead
|
|
* create responsive containers
provide more flexibility and allow the user to determine when containers switch from fluid to fixed width.
* fix the base container code
this commit fixes the non-media portion of the generated CSS. I learned about the `@extends` directive and was able to put it to good use.
I create a new temporary map that contains all the main `$container-max-widths` and join it to our 2 special cases of 'xs' and 'fluid'. Then we loop through that and, with the appropriate infixes, extend our placeholder
* formatting for style
forgot to run my tests before the last push, i think these are better.
* finish incomplete comment
* fix the responsive containers
using the `@extend` directive I was able to clean up this code
* fix responsive containers in the navbar
mostly we just look through all of our breakpoints so we can include all of the responsive container classes in the tweaks we have to do for the navbar (redeclaring flex properties, don't double up on padding, etc)
* Simplify container extends
* Simplify navbar containers
* Rearrange, add comments, ensure everything is nested in $enable-grid-classes
* Reduce new CSS by using attribute selector
We avoid using `@extend` whenever possible, and this is more readable
* Update _grid.scss
* Update _navbar.scss
* Add docs for responsive containers, redesign the container layout page
* Add to the Grid example
|
|
|
|
|
|
"Popovers whose both title..."
|
|
Fixed minor grammatical error:
"... the best method get scroll ..."
=>
"... the best method to get scroll ..."
|
|
* Update bs-custom-file-input.min.js to v1.3.2.
* Update anchor.min.js to v4.2.0.
|
|
Remove https://glyph.smarticons.co/ from list of suggestions.
The domain is now for sale and is triggers warnings in Firefox and Chrome
|
|
mixins
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adapted for v4-dev.
|
|
|
|
For some reason the old image was bad quality.
|
|
Checkboxes and radios use are built to support HTML-based form
=>
Checkboxes and radio buttons support ...
|
|
Corrected minor spelling error.
|
|
x-ref #28987
|
|
* Ensure correct active class is set on button toggles/checkboxes/radios on page load
Sanity check, ensures that the UI visually matches the actual values/states of controls. Also ensures that if any autocomplete/autofill happened, this is visually accounted for
by having the correct class set.
Includes unit tests (and `autocomplete` has been removed from these as it's no longer necessary)
* Remove now unnecessary autocomplete attribute
As the attribute was there to force/ensure that the visual presentation matched the state, and this is now taken care of programmatically, there's no need to unnecessarily suppress autocomplete...let them autocomplete if they want to...
|
|
|
