| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2018-12-21 | Prep for v4.2.0 release | Mark Otto | 1 | -1339/+0 | |
| - Move 4.1 docs to 4.2 - Update versions everywhere to 4.1.3 with release script - Manually bump the shorthand version in package.json - Add 4.2 to the versions docs page - Update some redirects - Fix tests asset URLs - Bump Nuget and more | |||||
| 2018-12-12 | Add switch custom form control (#23004) | Gijs Boddeus | 1 | -0/+16 | |
| 2018-11-28 | Revert "Use `h5` for callouts so that they are not included in ToC." | XhmikosR | 1 | -1/+1 | |
| This reverts commit 11da1601140174e4fa4e0e25e7f66fc21c08e927. This is no longer needed with jekyll-toc 0.9.1. | |||||
| 2018-11-27 | Use `h5` for callouts so that they are not included in ToC. | XhmikosR | 1 | -1/+1 | |
| Callouts are already excluded from ToC, but due to a limitation in jekyll-toc they are still being included. We should revisit this if the bug is fixed later. | |||||
| 2018-11-13 | Customize browse text of the custom file input with HTML (#27651) | Martijn Cuppens | 1 | -1/+13 | |
| 2018-11-07 | Wrap checkboxes in `.form-group` (#27624) | sts-ryan-holton | 1 | -5/+7 | |
| 2018-09-20 | Update forms.md | 719media | 1 | -4/+4 | |
| fix duplicate id attribute | |||||
| 2018-09-18 | use bsCustomFileInput in our documentation (#27264) | Johann-S | 1 | -1/+1 | |
| 2018-09-18 | Clarify docs for custom form structure | Mark Otto | 1 | -1/+1 | |
| Fixes #25440 | |||||
| 2018-08-18 | Recommend a plugin to animate custom file input (#27088) | Johann-S | 1 | -0/+5 | |
| 2018-08-12 | docs/4.1/components/forms.md: fix useiconic link. | XhmikosR | 1 | -1/+1 | |
| 2018-08-02 | Hyphenate client-side/server-side (#27016) | Jonathan | 1 | -1/+1 | |
| 2018-07-29 | Merge branch 'form-validation-icons' into v4-dev | Mark Otto | 1 | -3/+11 | |
| 2018-07-20 | Clarify custom select styles | Mark Otto | 1 | -1/+1 | |
| Fixes #26281 | |||||
| 2018-07-11 | Reorganize docs for easier deploys | Mark Otto | 1 | -0/+1296 | |
| With the current docs directory setup, I'm making too many mistakes and have to manually address path changes and directory moves on deploy. This makes for a frustrating experience developing locally and shipping releases. With this PR, we're basically back to the same setup from v3—duplicating the dist directory into our docs directory. Not the most ideal, but very straightforward for me as the release manager. | |||||
