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
28303	IntegerField & NumberInput widget localize max_value when rendering form field	Richard Owen	nobody	"This issue is a change / regression in Django 1.11. It works correctly with Django 1.10. Tested on Django 1.11.2 and Python 2.7.13.

== Reproduction Steps

1. Enable the following settings:

{{{
USE_L10N = True
USE_THOUSAND_SEPARATOR = True
}}}

2. Create a form with an IntegerField with a large max_value set:

{{{
class TestForm(forms.Form):
    integer_field = forms.IntegerField(max_value=999999)
}}}

== Expected Result
Form is rendered as
{{{
<input type=""number"" name=""integer_field"" max=""999999"" required id=""id_integer_field"" />
}}}

== Actual Result
Form is rendered as
{{{
<input type=""number"" name=""integer_field"" max=""999,999"" required id=""id_integer_field"" />
}}}

Note the comma separator in the max attribute on the input.

Internet Explorer 11 treats this field as having a max attribute of 999. So entering a value of 1000 in the field prevents the user from submitting the form."	Bug	closed	Forms	1.11	Release blocker	fixed			Accepted	1	0	0	0	0	0