-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why is is-valid added to form fields by default? #276
Comments
Yes, for GET forms this is very illogical, I agree. Use the workaround for now, I'm working on the similar problem in |
Thanks for the fast update. Can you update this issue if you fix the bootstrap5 version, in case you don't have time to backport it, I will try a PR. |
Looking at https://getbootstrap.com/docs/4.6/components/forms/#validation, it seems Bootstrap 4 advises against server side validation. A solution would be to default to |
Note that I got a stackoverflow answer https://stackoverflow.com/a/67145950/401226 which suggests: {% bootstrap_form filter.form layout='inline' bound_css_class='' %} However, this doesn't address the question of a sensible default. |
I may have to recheck, but I think this behavior was (at least originally) the same in django-bootstrap3. Bootstrap 4 does have a much more visible "Validated" look (Bootstrap 3 just does a green line around the field). |
I change to bootstrap4 from bootstrap3. I have a filter form on top of a table, rendered with
The field is rendered as
<input .... class="form-control is-valid"...>
the
is-valid
class means my field gets a big green tick even on the first page load (before submit)Bootstrap3 didn't do this decoration.
I realise I can prevent
is-valid
via settings for the BOOTSTRAP4 app, but why is this the default?The text was updated successfully, but these errors were encountered: