Would it make sense for ColdMVC to add the novalidate attribute to
forms by default when using <c:form>? I find the HTML 5 form
validation a little wonky and I think it might be best if developers
had to opt-in to using it.
I could also add the ability to configure it on/off by default using
your config.ini. For example, you'd be able to set
coldmvc.form.options.form.novalidate = true or something like that.
> Would it make sense for ColdMVC to add the novalidate attribute to > forms by default when using <c:form>? I find the HTML 5 form > validation a little wonky and I think it might be best if developers > had to opt-in to using it.
> I could also add the ability to configure it on/off by default using > your config.ini. For example, you'd be able to set > coldmvc.form.options.form.novalidate = true or something like that.
I would update the attribute to support boolean values, so that
<c:form novalidate="true" /> would add the novalidate attribute and
<c:form novalidate="false" /> would remove it if it existed.
FYI, negatively-named attributes and valueless attributes are
horrible.
On Dec 28, 10:57 am, Ryan Arneson <arne...@gmail.com> wrote:
> If you didn't add the config option, how would you get rid of the
> novalidate attribute from the form tag if you wanted to use it?
> On Wed, Dec 28, 2011 at 10:49 AM, Tony Nelson <tonynelso...@gmail.com>wrote:
> > Would it make sense for ColdMVC to add the novalidate attribute to
> > forms by default when using <c:form>? I find the HTML 5 form
> > validation a little wonky and I think it might be best if developers
> > had to opt-in to using it.
> > I could also add the ability to configure it on/off by default using
> > your config.ini. For example, you'd be able to set
> > coldmvc.form.options.form.novalidate = true or something like that.
> I would update the attribute to support boolean values, so that > <c:form novalidate="true" /> would add the novalidate attribute and > <c:form novalidate="false" /> would remove it if it existed.
> FYI, negatively-named attributes and valueless attributes are > horrible.
> On Dec 28, 10:57 am, Ryan Arneson <arne...@gmail.com> wrote: > > If you didn't add the config option, how would you get rid of the > > novalidate attribute from the form tag if you wanted to use it?
> > On Wed, Dec 28, 2011 at 10:49 AM, Tony Nelson <tonynelso...@gmail.com > >wrote:
> > > Would it make sense for ColdMVC to add the novalidate attribute to > > > forms by default when using <c:form>? I find the HTML 5 form > > > validation a little wonky and I think it might be best if developers > > > had to opt-in to using it.
> > > I could also add the ability to configure it on/off by default using > > > your config.ini. For example, you'd be able to set > > > coldmvc.form.options.form.novalidate = true or something like that.
