From 6c214ad4c242fcd76fce820d68a7df865a59ee6c Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Tue, 6 Jun 2017 11:27:29 -0700 Subject: [PATCH] drop the old validation styles and docs --- docs/4.0/components/forms.md | 133 ----------------------------------- scss/_forms.scss | 62 ---------------- scss/mixins/_forms.scss | 56 --------------- 3 files changed, 251 deletions(-) diff --git a/docs/4.0/components/forms.md b/docs/4.0/components/forms.md index 14f00259b9..d312071777 100644 --- a/docs/4.0/components/forms.md +++ b/docs/4.0/components/forms.md @@ -960,139 +960,6 @@ Our example forms show native textual ``s above, but form validation styl {% endexample %} -- To use, add `.has-warning`, `.has-danger`, or `.has-success` to the parent element. Any `.col-form-label`, `.form-control`, or custom form element will receive the validation styles. -- Contextual validation text, in addition to your usual form field help text, can be added with the use of `.form-control-feedback`. This text will adapt to the parent `.has-*` class. By default it only includes a bit of `margin` for spacing and a modified `color` for each state. -- Validation icons are `url()`s configured via Sass variables that are applied to `background-image` declarations for each state. -- You may use your own base64 PNGs or SVGs by updating the Sass variables and recompiling. -- Icons can also be disabled entirely by setting the variables to `none` or commenting out the source Sass. - -### Defining states - -Generally speaking, you'll want to use a particular state for specific types of feedback: - -- **Danger** is great for when there's a blocking or required field. A user *must* fill in this field properly to submit the form. -- **Warning** works well for input values that are in progress, like password strength, or soft validation before a user attempts to submit a form. -- And lastly, **success** is ideal for situations when you have per-field validation throughout a form and want to encourage a user through the rest of the fields. - -{% comment %} -{% callout warning %} -#### Conveying validation state to assistive technologies and colorblind users - -Using these validation styles to denote the state of a form control only provides a visual, color-based indication, which will not be conveyed to users of assistive technologies - such as screen readers - or to colorblind users. - -Ensure that an alternative indication of state is also provided. For instance, you can include a hint about state in the form control's `