aboutsummaryrefslogtreecommitdiff
path: root/site
AgeCommit message (Collapse)AuthorFilesLines
2020-09-02Docs: Add top/bottom margin to highlighted code samples (#31036)Patrick H. Lauke2-8/+8
* Add top/bottom margin to highlighted code samples provide more space to avoid having the "Copy" button overlap code sample content * Modify clipboard button style Per https://github.com/twbs/bootstrap/pull/31036#issuecomment-661322566 and https://github.com/twbs/bootstrap/pull/31036#issuecomment-668162630 * Tweak margin, clipboard button size and position Co-authored-by: XhmikosR <[email protected]>
2020-09-01Fix incorrect green and cyan hex codes (#31572)Arnaud Thomas D1-2/+2
2020-09-01Add default parameters to each border radius mixin (#31571)Jeremy Jackson1-0/+1
* Add default parameters to each border radius mixin * Add border radius changes to migration guide Co-authored-by: Jeremy Jackson <[email protected]>
2020-09-01docs: Fix typo on Customize -> Color page (#31556)Alex Plescan1-1/+1
Co-authored-by: XhmikosR <[email protected]>
2020-08-22Update icons.ymlŁukasz Holeczek1-0/+2
Add new icons set - CoreUI Icons
2020-08-19docs(typography): missing punctuation (#31505)Gaël Poupard1-1/+1
2020-08-17Mention that Edge Legacy also supports 'filling' their trackChristian Oliff1-1/+1
Edge Legacy support filling their track by default. Example: https://codepen.io/coliff/pen/VwaZgVZ
2020-08-17Remove 'both' as its no longer just 2 breakpoints (now that XXL is there)Christian Oliff1-1/+1
2020-08-05make breakpoints specifications consistent with layout/grid.mdmaks1-1/+1
0-576px could be misinterpreted "up to 576px included"
2020-08-05docs: Fix issue number typo in migrationkyletsang1-1/+1
2020-08-04box-shadow() mixin allow 'null' and drop support 'none' with multiple args ↵Shohei Yoshida1-0/+1
(#30394) * Support 'null' and drop `none` with multiple args * Output a warning when use 'none' with multiple arguments * Add migration note * Update migration.md Co-authored-by: Mark Otto <[email protected]> Co-authored-by: XhmikosR <[email protected]>
2020-08-04Add view on GitHub links for easier content editing from the docs (#31339)Mark Otto1-1/+4
* Add view on GitHub links for easier content editing from the docs * Update docs.html * Move to .btn-bd-light Co-authored-by: XhmikosR <[email protected]>
2020-08-03Added opacity-75 and opacity-50 classesMohammad Ali Shahbazi1-0/+31
2020-08-03Fixed typo in docs v5 (Utilities/API) pageMohammad Ali Shahbazi1-4/+4
2020-08-03Update migration guide (#31387)Mark Otto1-12/+15
* Document change to form check and radio size * Update todos in Migration guide Co-authored-by: XhmikosR <[email protected]>
2020-08-02Add padding to badges (#31132)Patrick H. Lauke1-0/+4
* Add padding to badges The current badges are very tightly padded, and because the top and bottom padding are the same, and aligned to the baseline, this makes badges with descenders (e.g. the "g" in "Danger") look uncomfortably close to the bottom. Adding more ample padding masks this a bit. An alternative would be to have separate top and bottom padding, with the bottom one slightly larger than the top - but conversely, that then makes badges that contain no text with descenders, and particularly badges that contain all uppercase characters, look too bottom-heavy. Also adding some left/right extra padding, as currently the pill badges look uncomfortably tight on the sides due to the rounding.
2020-07-31Update copy around breakpoint sizing (#31382)Mark Otto1-2/+1
* Update copy around breakpoint sizing Fixes #31288 * Update breakpoints.md * Further copy changes Co-authored-by: XhmikosR <[email protected]>
2020-07-31Add accessibility note about dismissible alerts and focus (#31358)Patrick H. Lauke1-2/+7
2020-07-31Cleanup/fix after the sr-only to visually-hidden renaming (#31359)Patrick H. Lauke1-25/+0
* sr-only -> visually-hidden cleanup It seems the old screen-readers.md file was left behind, and forgot to rename the mixin * Fix broken mixins for visually-hidden
2020-07-21Add toasts to the components requiring JavaScript (#31344)Rohit Sharma1-0/+1
2020-07-13docs(skippy): prevent skip links from overlapping headerGaël Poupard2-11/+22
2020-07-13Sort the versions from the latest to the oldest.XhmikosR1-1/+1
2020-07-13Improve spacingMark Otto1-1/+1
2020-07-13Update version.md to include v5Laim1-1/+1
Version.md on v5.getbootstrap.com is only referring to v1 > v4 when it should be referring to v1 > v5.
2020-07-13Migration update (#31278)Mark Otto1-2/+18
* Clarify screen reader changes * Add some docs and reboot notes to migration guide * Add mention of docs renaming of screen reader helper page * Mention null vars from navs PR at #31035 * Update migration.md Co-authored-by: Patrick H. Lauke <[email protected]> Co-authored-by: XhmikosR <[email protected]>
2020-07-13v5: Tweak some colors (#31276)Mark Otto1-0/+7
* Tweak green and cyan colors, bump min contrast ratio to 4.5 Co-authored-by: XhmikosR <[email protected]>
2020-07-12toasts: make default duration 5s (#31109)Rohit Sharma2-1/+5
Co-authored-by: XhmikosR <[email protected]>
2020-07-12Easier disabled state customization for button variants (#30639)Gaël Poupard1-0/+4
* feat(buttons): easier disabled state customization * docs(migration): mention new arguments for disabled state in button-variant() * Update migration.md Co-authored-by: XhmikosR <[email protected]> Co-authored-by: Mark Otto <[email protected]>
2020-07-11Docs: forms accessibility cleanup (#31114)Patrick H. Lauke5-28/+31
* 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-11Fix docs sass importing example.Florian Lacreuse1-1/+2
2020-07-11Update layout.mdMark Otto1-1/+1
2020-07-11Single line example for inline formsRohit Sharma1-5/+0
2020-07-10Rename `sr-only` to `visually-hidden` in new/renamed helper doc filePatrick H. Lauke1-6/+6
2020-07-10Add alias/redirectPatrick H. Lauke1-0/+1
2020-07-10Reword slightly awkward-sounding descriptionPatrick H. Lauke1-1/+1
2020-07-10Emphasise/call out the note about `.invisible` and ATPatrick H. Lauke1-1/+5
2020-07-10Docs: rename "Screen readers" helper page to "Visually hidden"Patrick H. Lauke3-2/+27
"screen readers" is quite reductive, as there are other assistive technologies. content hidden this way is even announced by things like Alexa/Siri etc, so it's not so much just "screen readers". in the long run, we may even consider changing the actual classnames (maybe `.visually-hidden` / `.visually-hidden-focusable`, though admittedly that's a bit verbose). also includes a tiny tweak to layout.md to generalise the note about using `.sr-only`
2020-07-07Fix some hexa in colors docs. (#31254)Florian Lacreuse2-5/+5
2020-07-06Docs: separate button group out of checks/radios, expand button groups page ↵Patrick H. Lauke2-69/+115
(#31201) * Keep checks/radio toggle buttons on topic - give examples of the pure toggle checks and radios, without the button group class. show that these work fine without `.btn-group`, but still cross-reference it - move the explanation from "Checkbox toggle buttons" directly to "Toggle buttons", as the mention of using button classes applies equally to the subsequent "Radio toggle buttons" and "Outlined styles" subsections. * Expand button group description as it's not just single line, but vertical as well * Expand button group examples - add more colour ... `.btn-secondary` is just dull and uninspiring - new section to showcase "Checkbox and radio button groups" - add a mixed styles example - add an example of vertical radio button group
2020-07-03Fix sidebar jump (#31232)Martijn Cuppens2-15/+12
2020-07-03Rename `sr-only`/`sr-only-focusable` (#31139)Patrick H. Lauke15-82/+87
* 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-07-03Docs: improve/expand button documentation (#31093)Patrick H. Lauke2-4/+12
* Docs: improve/expand button documentation - since we're not doing the disabled cursor thing anymore anyway, remove confusing/unnecessary mention for link-based disabled buttons - make the disabled toggle example using a link actually follow the preceding advice of also having `tabindex="-1"` and `aria-disabled="true"` - tweak the link functionality callout to also still mention `aria-disabled` to reinforce the idea - tweak toggle state description (not just `<button>`s, but also links etc...so just remove mention of `<button>` there; also reinforce accessibility aspect once more) - add a new callout that cross-references checkbox-based toggles, and what the similarity/difference between them is - add a matching cross-reference callout to the checkbox-based toggle buttons page * Update link to now renamed checks-radios.md
2020-07-03Docs: clarify that pointer events classes don't affect keyboard interaction ↵Patrick H. Lauke1-3/+7
(#31134) * Docs: clarify that pointer events classes don't affect keyboard interaction * Neutralise example links that are `pe-none`
2020-07-01Fix generated example code for RFS (#31213)Sascha Nuissl1-1/+1
Co-authored-by: Martijn Cuppens <[email protected]>
2020-07-01Update migration.md (#31122)XhmikosR1-31/+50
* Add a new v5.0.0-alpha2 section * Add missing Browser versions from v5.0.0-alpha1
2020-07-01Remove extra spaceXhmikosR4-4/+4
2020-07-01homepage-hero.svg: move `defs` before `g`XhmikosR1-1/+1
2020-07-01Use the site param for iconsXhmikosR2-2/+2
2020-06-30homepage: Fix wrong indentation (#31211)XhmikosR1-2/+2
2020-06-27Fix spelling mistake (#31190)Alex Mohr1-1/+1
Co-authored-by: Alex Mohr <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2026-06-10 06:44:35 +0000