bootstrap - The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

Age	Commit message (Collapse)	Author	Files	Lines
2022-05-13	Prepare v5.2.0-beta1	Mark Otto	1	-167/+0

2022-02-23	Docs: replace CSS by utilities in examples (#35699)	Julien Déramond	1	-6/+6
	* Drop .opacity-50 and .opacity-75 redefinition in examples * Drop unused .card-img-right from blog example CSS files * Use line-height utilities when possible * Use rounded-* utilities in examples * Replace .nav-underline by .nav-scroller and use it in examples.html default * Use .mb-1 for .blog-post-title * Remove unused CSS rule and use .fw-* utilities for carousels examples * Use utilities for cheatsheet examples * Extract some CSS to utilities for .nav-masthead .nav-link in cover example * Dashboard group of minor modifications * Dropdowns example: refactoring * Dropdowns example refactoring: fix linting by removing selector by id * Features example refactoring * Headers example refactoring * List groups example refactoring * Sidebars example refactoring * Sign-in example refactoring * Starter template refactoring * Fix RTL examples Co-authored-by: Mark Otto <[email protected]>
2021-11-01	Add missing `role="search"` and `type="search"` in navbar doc and examples ↵	Julien Déramond	1	-1/+1
	(#35223) * Add missing `role="search"` and `type="search"` in navbar doc and examples * Update site/content/docs/5.1/components/navbar.md * Remove warning callout about ensuring correct search role in navbar doc Co-authored-by: Gaël Poupard <[email protected]> Co-authored-by: XhmikosR <[email protected]>
2021-09-06	Disabled link cleanup (#34886)	Patrick H. Lauke	1	-1/+1
	* Disabled link cleanup per https://www.w3.org/TR/html-aria/#docconformance > It is NOT RECOMMENDED to use `aria-disabled="true"` on an `a` element with an `href` attribute. > >NOTE >If a link needs to be "disabled", remove the `href` attribute. This PR removes the unnecessary `href="#"`, `tabindex="-1"`, and `aria-disabled="true"` from disabled links in both docs pages and examples. `aria-disabled="true"` is kept for disabled link-based buttons (that have `role="button"`) as there it's appropriate to use (you want to convey to assistive technologies that this thing you're claiming is a button is also disabled at the moment) Further, the PR extends the "Link functionality caveat" to show the "proper" way (removing `href` and adding `.disabled` class only) to disable a link, but then explains what to do if that's not possible (and then keeps an example with all the traditional `href="#" tabindex="-1" aria-disabled="true"`, but explains clearly that it's not ideal). Same sort of explanation is also added to the pointer event utilities page * Turn big note into actual normal doc text Co-authored-by: Mark Otto <[email protected]> Co-authored-by: Mark Otto <[email protected]> Co-authored-by: XhmikosR <[email protected]>
2021-08-04	Prepare v5.1.0. (#34674)v5.1.0	XhmikosR	1	-0/+167