I also noticed an issue with this today where you cannot render an input[type="number"] which supports decimals using the Form component.

The HTML5 number input does support decimals, and this should be reflected in either the NumberType or the IntegerType. It obviously makes far more sense with the NumberType, and I propose adding a new option to this form type to render it as a strict number input type (strict maybe?)

ping @webmozart

See #8106

Just adding my opionion about the validation rules:

An integer is an integer. Every integer type should have validation constraints added by default, not allowing non integer input. Otherwise there is no benefit over useing a regular text field and adding custom validation constraints.

The symfony form number type should also have a "step" option that would than be mapped to the html5 input type="number" step option. Than it would e.g. be possible to have float numbers that would only be a full number or a .5 number with step=".5"

Another year has passed and still nothing has happend here.

I can confirm that NumberType renders to <input type="text" ... > and not as expected to <input type="number" ... > in version 3.0.6.

At this point this might be worth noting: /src/Symfony/Bridge/Twig/Resources/views/Form/form_div_layout.html.twig#L135
The comment was added in 4c0d53a back in 2011. Since then things have changed and I'd say the statement is wrong. The type="number" definitely can handle floats. It also has this neat attribute called 'step' as mentioned by @ghost almost a year ago.

I'd love to see this corrected in the next version because especially on smartphones it's more convenient to have it as type="number" instead of plain text.

Also see #8106 which basically states the same as this issue.

@ghost step can already be added through attr

@stof yes sure. But if NumberType would render into type="number" then it'd be nice to have a default value like step="any".

I think the field types have moved on slightly since this was opened, but now there is the issue of IntegerType supporting non-integer values when it would make more sense to have this support in a NumberType instead (with the localised string support like I mentioned in my original comment).

I doubt this will ever be changed now as it would break BC

Isn't it an option to add a widget option for the NumberType (similar to DateType), with a default of text, but add an option for number. That could be without BC breaks, right?

Just came across this issue. It really doesn't make any sense to me that IntegerType allows decimal numbers and there is no flag to disable it. Who thinks that 1.23 is integer?