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
2021-08-04	Prepare v5.1.0. (#34674)v5.1.0	XhmikosR	1	-316/+0

2021-02-10	Add Sass docs (variables, mixins, and loops) to most pages (#32747)	Mark Otto	1	-0/+6
	* 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]>
2021-01-28	Update checks and radios in input groups (#32912)	Mark Otto	1	-3/+3
	- Adds .mt-0 to the examples - Zero-ing out universally for all of them like in #32896 would cause issues for those who include the input with visible label text, where the text and input would be misaligned
2020-12-04	docs(examples): new cheatsheet and RTL examples	Gaël Poupard	1	-3/+3

2020-11-14	Add `bs` in data attributes	Rohit Sharma	1	-6/+6
	- Add `bs` in data APIs everywhere - Update unit tests
2020-11-03	Form file docs and overrides (#32058)	Gaël Poupard	1	-8/+8

2020-10-28	Drop custom file upload plugin in favor of CSS	Martijn Cuppens	1	-28/+4

2020-10-27	Add example with input group between two inputs	Jonathan	1	-0/+6

2020-07-11	Docs: forms accessibility cleanup (#31114)	Patrick H. Lauke	1	-6/+0
	* Expand on disabled fieldsets and faked buttons include further advice/information on how to disable faked buttons for keyboard/AT users * Centralise accessible name advice in forms overview seems odd to only mention (separately) label, aria-label etc in input-group and layout. the advice is just as pertinent in other sections like select. checks only skims over this. moving this, in expanded form, into the overview section itself. adding a specific cross-reference (just because they are easily left with no accname at all) in the checks page. * Change warning about accessibility, modify server-side example - paradoxically, due to our current problems with validation (see #28414) and the fact that browsers seem to have improved in this area for the most part, it's now actually better to use browser-native validation - added explicit `id` and `aria-describedby` association to at least the server-side form error messages, to show how it should be done properly, and expanded the prose for that explaining this. * Replace `.sr-only` with `.visually-hidden` in new addition * Copy edits for clarity in parenthetical * Copy and formatting tweaks - Wordsmithing here and there - Turns some hyphens into em dashes - Turns a long running comma separated list into an unordered list - Rearranges some copy just a bit Co-authored-by: Mark Otto <[email protected]>
2020-07-03	Rename `sr-only`/`sr-only-focusable` (#31139)	Patrick H. Lauke	1	-3/+3
	* 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]>
2020-05-13	Bump version to 5.0.0-alpha1 (#29925)	XhmikosR	1	-0/+334
	Also add v4.5.0 in versions and keep README.md pointing to v4.5.0 so that there are no broken stuff.