Django can apply classes to input elements or other field widgets, either at a field declaration or at a runtime in form's initializer. For example, Mezzanine does it itself at several places like in HTML5Mixin <https://bitbucket.org/stephenmcd/mezzanine/src/022a65d7ec313a70434dc195bed536157267da7d/mezzanine/core/forms.py?at=default&fileviewer=file-view-default#forms.py-14>, EditForm etc. In a similar way I have to do it at startup by monkey-patching original mezzanine form classes. I'd imagine Mezzanine would accordingly set appropriate css-classes for all its non-static generated contents, allow fully utilize existing Bootstrap code and not reinventing a wheel.
Now Mezzanine produces input fields without form-control attribute, so all optional or variant attributes applied on outer .form-group or form simply do not work. Because some of existing style combinations were forgotten, when simulating bootstrap features, like mentioned horizontal or inline forms. Sure, you can hardcode missing style combinations but it is a bit tiresome and doubtful, when almost identical and standardized solution already does exist. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
