[RFC] HTML5 input types for form fields

[Vinny]

Everyone knows that the phpBB 3.1 uses HTML5, thinking about it why not use the new features? The discussion about the new features started here.

Proposal
Add the new input types for forms. With the new HTML5 input types, you can have more control over each field, well as validating email and url fields.

Pros
The browser will automatically take care to validate the fields.

Cons
Browsers support . Some browser doesn't support some types. But the current error box system will remain.

Ticket: http://tracker.phpbb.com/browse/PHPBB3-11010
PR: https://github.com/phpbb/phpbb3/pull/1000/

[nextgen]

Cons
Browsers support . Some browser doesn't support some types.

In this case only is Internet explorer, Firefox, Opera, Safari and Chrome already support the features of HTML5

Proposal
Add the new input types for forms. With the new HTML5 input types, you can have more control over each field, well as validating email and url fields.

+1

[Vinny]

In this case only is Internet explorer, Firefox, Opera, Safari and Chrome already support the features of HTML5

FYI: http://fmbip.com/ tells you about your current browser compatibility.

Also, look this: http://www.w3schools.com/html5/html5_fo ... _types.asp

[naderman]

Seems straight forward, and even if some browser doesn't support one of them yet, worst case it'll look like it does now. So I think all we need here is for someone to create a ticket and someone who wants to implement it who will send a pull request.

[Vinny]

Seems straight forward, and even if some browser doesn't support one of them yet, worst case it'll look like it does now.

Yes, good point.

So I think all we need here is for someone to create a ticket and someone who wants to implement it who will send a pull request.

Ticket = Done
PR = I'm working in the pr.

[Vinny]

I was reviewing and testing the new types and I think that just email and url should be used.

Opinions?

[A_Jelly_Doughnut]

I could certainly see scenarios where date, datetime, and tel[ephone] would be useful, although only date is currently implemented as a CPF type.

[Vinny]

Maybe number and search too.

[callumacrae]

The search input annoyed me because it wasn't themeable. I couldn't get rid if the overly-rounded corners.

[Pony99CA]

Seems straight forward, and even if some browser doesn't support one of them yet, worst case it'll look like it does now.

As long as "legacy" browsers still work with the new field types, I don't see much downside to this. It might also make my New Custom Profile Field Types RFC easier (in the future; for now, validation will still be required anyway).

I could certainly see scenarios where date, datetime, and tel[ephone] would be useful, although only date is currently implemented as a CPF type.

CPF? UPDATE: Never mind -- Custom Profile Field.

The Month type could be used for birth dates and the Color type in the ACP (for example, the Group colour setting).

Steve