Description: ------------ With the arrival of the new HTML5 input types it would be nice to see them appear as QuickForm2 Elements. search tel url email datetime date month week time datetime-local number range color

+1 to this; browser support is documented @ http://diveintohtml5.org/forms.html

class HTML_QuickForm2_Element_InputText extends HTML_QuickForm2_Element_Input { protected $attributes = array('type' => 'text'); } class HTML_QuickForm2_Element_InputEmail extends HTML_QuickForm2_Element_Input { protected $attributes = array('type' => 'email'); } ... etc

Do the maintainers have an opinion on the architecture of supporting this? Just following the current pattern leads to a minor class explosion, with HTML_QuickForm2_Element_InputSearch apparently equal in status to HTML_QuickForm2_Element_InputText. On the other hand, gathering them in one class could be nonintuitive, since "…InputText" doesn't obviously cover the new types, and a new name (such as "InputTextlike") would be hard to guess. I'm leaning toward the class-explosion option myself, though maybe the new classes should extend "…InputText". (I'm asking because my project lead is demanding a minimum value on the spinner I gave him by doing setType('number') on an HTML_QuickForm_input. I'm considering patching HTML5 types in, after upgrading to HTML_QuickForm2.)

Any news on this? It would be great to have url, email ... input types. for example IOS devices show a different keyboard when focusing special input types.

What is the status about this? Will this be added?