| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
* 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]>
|
|
They're links, acting as links. Just because they're styled as buttons visually doesn't mean they need/get `role="button"`
|
|
* Hyphen to dash for ranges
* Hyphen to dash for ranges
* Hyphen to dash for ranges
* Hyphen to dash for ranges
* Hyphen to dash for ranges
|
|
The "active" CSS class must be on "nav-link" element, see `_navbar.scss`:
```css
.nav-link.active {
color: $navbar-dark-active-color;
}
```
Co-authored-by: XhmikosR <[email protected]>
|
|
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/
|
|
|
|
- Add `bs` in data APIs everywhere
- Update unit tests
|
|
* 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]>
|
|
Also add v4.5.0 in versions and keep README.md pointing to v4.5.0 so that there are no broken stuff.
|
