If matters, +1.

People can easily change from $('input[type=text]') to
$('input[type=text],input[type=email]'), it's a easy, no pain change, with
various benefits of HTML5 fields.

I would only suggest that people can do something like
number_field=IntegerField(html5=False) in form (at least in 1.5) so fields
back to input type=text in rendering and who don't wanna touch css/js and
third party apps to fix the code, just put this and everything works.

Felipe 'chronos' Prenholato.
Linux User nº 405489
Home page: http://devwithpassion.com | http://chronosbox.org/blog
GitHub: http://github.com/chronossc/ | Twitter: http://twitter.com/chronossc


2012/10/1 Stephen Burrows <stephen.r.burr...@gmail.com>

> Hey all - Last I heard, today was the last day for new features for 1.5. I
> was triaging tickets yesterday and ran this ticket. [1] The ticket looks
> fine, and it addresses the issues raised here. The only new issue (raised
> on the ticket) is that this change could break third-party javascript and
> css if anyone is relying on those fields having type="text". Although this
> is a valid concern, I still think it would be worth switching over to HTML5
> at long last – perhaps with a slightly more explicit warning in the
> backwards-compatibility section of the release notes so that designers know
> they need to watch out for that.
>
> Since the only obstacle seems to be getting some sort of consensus among
> core devs that this is a change that's okay to make, I was hoping to get
> some feedback, and maybe get the patch merged in.
>
> Best,
> Stephen
>
> [1] https://code.djangoproject.com/ticket/16630
>
> On Tuesday, December 27, 2011 8:15:19 AM UTC-8, Jonas H. wrote:
>
>> This patch has been around for while now. I just updated the patch so it
>> applies cleanly against rev 17281.
>>
>> So, can we get this patch into trunk or is something missing?
>>
>> Jonas
>>
>> --
>> http://jonas.lophus.org | http://django-mongodb.org
>>
>> Want to become a Django MongoDB Engine/Django-nonrel core developer?
>> Get in touch: django-non...@**googlegroups.com
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/FSBHz8GBxAIJ.
>
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to