| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Co-authored-by: Rohit Sharma <[email protected]>
Co-authored-by: XhmikosR <[email protected]>
|
|
* docs(carousel): double-spaces out there
* docs(toasts): missing word, ins't it?
* docs(cheatsheet): use buttons for carousels and tabs ion cheatsheets too
Co-authored-by: XhmikosR <[email protected]>
|
|
* WIP: Mention variables, mixins, and loops in docs
* Add Sass sections to component pages
* add sass docs for forms and content
* Update buttons.md
* Remove empty mixins sections
* Massive update to utilities and some consistency changes
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
* Carousel: use buttons, not links, for prev/next
- expand the styles to neutralise border/background
- change docs page
- add extra unit test to check that links or buttons work as controls
- modify visual test to use buttons as well
- use buttons instead of links for prev/next
- remove `role="button"` from links that are actually links
* Clarify that controls can be button or link
* Update site/content/docs/5.0/components/carousel.md
Co-authored-by: Mark Otto <[email protected]>
* Explicitly set padding to 0 to prevent dipping/moving on active in Firefox
Co-authored-by: XhmikosR <[email protected]>
|
|
based on changes made in the backport https://github.com/twbs/bootstrap/pull/32639
|
|
* Add an actual `data-touch="false"` example in the carousel docs
this can also make it easier to actually check/debug any issues we may have with this data attribute
* Correct attribute table explanation and remove slide class from example
|
|
english language) text (#32246)
Replaces shorter examples with more sensible/representative/inforrmative text. For longer passages, resorted to using SFW extracts from http://katyperryipsum.com/
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
- Add `bs` in data APIs everywhere
- Update unit tests
|
|
|
|
This reverts commit 5c6925385ee926a749ead6a4f2ebbfc64e701f36.
|
|
Remove the `markdownify` call, and instead rely on Hugo's proper syntax; `{{% callout %}}` when we want to the content to be processed as Markdown.
This allows for stuff like:
{{% callout info %}}
##### I'm an info callout!
```css
.foo {
color: #fff;
}
```
{{< example >}}
<div class="alert alert-warning alert-dismissible fade show" role="alert">
<strong>Holy guacamole!</strong> You should check in on some of those fields below.
<button type="button" class="btn-close" data-dismiss="alert" aria-label="Close"></button>
</div>
{{< /example >}}
{{% /callout %}}
|
|
(#31809)
|
|
|
|
* Replace existing carousel control icons with chevrons from Bootstrap Icons
* Add .carousel-dark variant
* Test
* Add variable for .carousel-dark filter
* Update _variables.scss
Co-authored-by: XhmikosR <[email protected]>
|
|
* Rename `sr-only`/`sr-only-focusable`
To be more representative of the fact that these are not necessarily "screen reader" specific, but actually apply to assistive technologies in general (and also things like Alexa/Siri/etc). Goes hand-in-hand with #31133
Co-authored-by: XhmikosR <[email protected]>
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
Also add v4.5.0 in versions and keep README.md pointing to v4.5.0 so that there are no broken stuff.
|