diff options
| author | Jonathan <[email protected]> | 2019-03-04 14:52:13 +0100 |
|---|---|---|
| committer | XhmikosR <[email protected]> | 2019-03-04 15:52:13 +0200 |
| commit | c8361e2adf5a4d22d7ecd347d8b53a3d2c1f3af3 (patch) | |
| tree | 992e3d114f2c1d180e9bc987e33bbccc0c2e48fa | |
| parent | 19aee321a027edaa60c3087bfcf6c9f1517c9b98 (diff) | |
| download | bootstrap-c8361e2adf5a4d22d7ecd347d8b53a3d2c1f3af3.tar.xz bootstrap-c8361e2adf5a4d22d7ecd347d8b53a3d2c1f3af3.zip | |
Hyphenate server-side (#28401)
| -rw-r--r-- | scss/_forms.scss | 2 | ||||
| -rw-r--r-- | site/docs/4.3/components/forms.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/scss/_forms.scss b/scss/_forms.scss index 79ca507f7..e31a47312 100644 --- a/scss/_forms.scss +++ b/scss/_forms.scss @@ -240,7 +240,7 @@ textarea.form-control { // Provide feedback to users when form field values are valid or invalid. Works // primarily for client-side validation via scoped `:invalid` and `:valid` // pseudo-classes but also includes `.is-invalid` and `.is-valid` classes for -// server side validation. +// server-side validation. @each $state, $data in $form-validation-states { @include form-validation-state($state, map-get($data, color), map-get($data, icon)); diff --git a/site/docs/4.3/components/forms.md b/site/docs/4.3/components/forms.md index a3ad78e7a..b329f989a 100644 --- a/site/docs/4.3/components/forms.md +++ b/site/docs/4.3/components/forms.md @@ -752,13 +752,13 @@ Here's how form validation works with Bootstrap: - HTML form validation is applied via CSS's two pseudo-classes, `:invalid` and `:valid`. It applies to `<input>`, `<select>`, and `<textarea>` elements. - Bootstrap scopes the `:invalid` and `:valid` styles to parent `.was-validated` class, usually applied to the `<form>`. Otherwise, any required field without a value shows up as invalid on page load. This way, you may choose when to activate them (typically after form submission is attempted). - To reset the appearance of the form (for instance, in the case of dynamic form submissions using AJAX), remove the `.was-validated` class from the `<form>` again after submission. -- As a fallback, `.is-invalid` and `.is-valid` classes may be used instead of the pseudo-classes for [server side validation](#server-side). They do not require a `.was-validated` parent class. +- As a fallback, `.is-invalid` and `.is-valid` classes may be used instead of the pseudo-classes for [server-side validation](#server-side). They do not require a `.was-validated` parent class. - Due to constraints in how CSS works, we cannot (at present) apply styles to a `<label>` that comes before a form control in the DOM without the help of custom JavaScript. - All modern browsers support the [constraint validation API](https://www.w3.org/TR/html5/sec-forms.html#the-constraint-validation-api), a series of JavaScript methods for validating form controls. - Feedback messages may utilize the [browser defaults](#browser-defaults) (different for each browser, and unstylable via CSS) or our custom feedback styles with additional HTML and CSS. - You may provide custom validity messages with `setCustomValidity` in JavaScript. -With that in mind, consider the following demos for our custom form validation styles, optional server side classes, and browser defaults. +With that in mind, consider the following demos for our custom form validation styles, optional server-side classes, and browser defaults. ### Custom styles |