Closed variable closed 8 years ago
Hi. Yes, floppyforms behaves different there as it wants to output HTML5 forms in all it's facets. The differences are documented here: http://django-floppyforms.readthedocs.org/en/latest/differences.html?highlight=novalidate
Please make sure to read the section about novalidate
to see how you can avoid the client side (in-browser) validation.
I am using extra_views in conjunction with floppyform forms.
So this generates the inline forms, but the extra empty forms will have the html5 attribute "required" added to required fields. This results empty inline forms cannot be saved.
To solve this issue, I just needed to change from
to
This looks like the ModelForm from floppyform package is not doing exactly the same stuff as the vanila django ModelForm.