Re: on type-specific input fields

2014-08-16 Thread Erik Romijn
oesn't seem to be an issue as browsers which don't > > support that attribute (iOS, Android browsers) don't prevent form > > submission at all so they already have a "" behavior. > > > > Cheers, > > Bruno > > > > On Wed, Jul 23, 2014 a

Re: on type-specific input fields

2014-07-23 Thread patrickk
't seem to be an issue as browsers which don't > > support that attribute (iOS, Android browsers) don't prevent form > > submission at all so they already have a "" behavior. > > > > Cheers, > > Bruno > > > > On Wed, Jul 23, 2014 at 11:34 AM,

Re: on type-specific input fields

2014-07-23 Thread Aymeric Augustin
mission at all so they already have a "" behavior. > > Cheers, > Bruno > > On Wed, Jul 23, 2014 at 11:34 AM, Erik Romijn <erom...@solidlinks.nl> wrote: >> Hello all, >> >> Since Django 1.6, the Django form fields for URLs, numbers and email >> a

Re: on type-specific input fields

2014-07-23 Thread Bruno ReniƩ
..@solidlinks.nl> wrote: > Hello all, > > Since Django 1.6, the Django form fields for URLs, numbers and email > addresses make use of widgets that use type-specific input fields in their > HTML rendering. So instead of rendering them as , they now > have type="url&q

on type-specific input fields

2014-07-23 Thread Erik Romijn
Hello all, Since Django 1.6, the Django form fields for URLs, numbers and email addresses make use of widgets that use type-specific input fields in their HTML rendering. So instead of rendering them as , they now have type="url", type="number" and type="email".