Re: HTML5 support in QuickForm2
| From: | Alexey Borzov | Date: | Thu, 14 Apr 2011 19:05:40 +0000 |
| Subject: | Re: HTML5 support in QuickForm2 | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54212@lists.php.net to get a copy of this message | ||
Hi Daniel,
On 13.04.2011 2:26, Daniel O'Connor wrote:
Bear in mind that you still need server-side validation for new field types.[1] http://pear.php.net/bugs/bug.php?id=5308 [2] http://pear.php.net/bugs/bug.php?id=17842 [3] http://quickform.mamasam.com/wiki/doku.php?id=html5I reckon it's worth keeping as simple as possible for the moment. When I was mucking around with some of the pages in PEAR; I got away with implementing the simple extend -> override attribute type pattern.
IE: http://test.pear.php.net/package-new.php and http://svn.php.net/viewvc/pear/pearweb/trunk/public_html/package-new.php?view=log I got to put in other attributes, like @required and @placeholder easily enough via the existing API. A warning that element X includes a @required attribute but has no corresponding rule would be useful.Adding the rule automatically will be even more useful...
Not to rush things; but it would be great to have a number of simple controls in a release - input types url, email - so that I can remove them from the pearweb code.Yep, judging from current browser support it only makes sense to implement the simpler stuff. Calendars and color-pickers are quite difficult to emulate and are only natively supported by Opera. Anyway, I'm currently working on "live" client-side validation (similar to old DHTMLRulesTableless) that will be useful even without HTML5. Once it is ready it should be easy enough to add HTML5 validation support for browsers that implement it and add emulation for other browsers.