Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.3.2

Request #17842 Support for HTML5 form input methods
Submitted: 2010-09-03 19:58 UTC
From: nickcharsley Assigned:
Status: Open Package: HTML_QuickForm2 (version 0.4.0)
PHP Version: 5.3.3 OS: N/A
Roadmaps: 2.1.0    

 [2010-09-03 19:58 UTC] nickcharsley (Nick Charsley)
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


 [2011-03-27 11:43 UTC] doconnor (Daniel O'Connor)
 [2011-03-27 11:43 UTC] doconnor (Daniel O'Connor)
+1 to this; browser support is documented @
 [2011-03-27 12:07 UTC] doconnor (Daniel O'Connor)
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
 [2013-06-24 02:58 UTC] lastorset (Leif Arne Storset)
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.)
 [2013-12-11 17:36 UTC] caplod (Stefan Mielke)
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.
 [2016-11-12 20:37 UTC] stijnhau (Stijn Haulotte)
What is the status about this? Will this be added?