id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
23075	Type-specific input fields cause cross-browser issues and wrong error messages	Patrick K	nobody	"Django recently introduced a NumberInput which is rendered with type=""number"". While this seems like a good idea at first view, it leads to a couple of issues with different browsers:

a) Safari removes (!) any invalid values from this input field. This leads to unpredictable situations when trying to save with the admin.
b) Other browsers render non stylable error messages before (!) saving the form: This contradicts the standard Django form behaviour with the admin, when error messages are shown after (!) the form is being submitted.

I suggest using type=""text"" for any NumberInput or remove the field altogether. The current behaviour with this field is cross-browser madness and a conflict with how Django handles errors with forms."	Bug	closed	Forms	1.7-rc-1	Normal	fixed		sehmaschine@…	Ready for checkin	1	0	0	0	0	0