I was just wondering whether you would consider adding native support for HTML5 controls where the browser supports it?
My main use-case is for building mobile friendly forms where the native HTML5 controls provide convenient end user functionality targeted for that device - e.g. date and time pickers.
Off the top of my head the datatypes/controls that would benefit from this are:
xs:date/xf:date an the associated <xf:input> being rendered as HTML5 <input type="date"/> and <input type="time"/> respectively.</xf:input>
Similary xs:integer/xf:integer and xs:decimal/xf:decimal could be rendered in HTML5 as <input type="number"/>
Furthermore the <xf:range> could be rendered as <input type="range"/></xf:range>
If the browser is not HTML5 enabled I would suggest that the output should default to current behaviour. I also appreciate that not everyone would necessarily want HTML5 controls even for HTML5 browsers so it might benefit from being controlled via configuration or an XSLTForm specific annotation on the XForm control.
What do you think? Are there any other users that would welcome such a feature?
Thanks,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Alain,
I was just wondering whether you would consider adding native support for HTML5 controls where the browser supports it?
My main use-case is for building mobile friendly forms where the native HTML5 controls provide convenient end user functionality targeted for that device - e.g. date and time pickers.
Off the top of my head the datatypes/controls that would benefit from this are:
xs:date/xf:date an the associated <xf:input> being rendered as HTML5 <input type="date"/> and <input type="time"/> respectively.</xf:input>
Similary xs:integer/xf:integer and xs:decimal/xf:decimal could be rendered in HTML5 as <input type="number"/>
Furthermore the <xf:range> could be rendered as <input type="range"/></xf:range>
If the browser is not HTML5 enabled I would suggest that the output should default to current behaviour. I also appreciate that not everyone would necessarily want HTML5 controls even for HTML5 browsers so it might benefit from being controlled via configuration or an XSLTForm specific annotation on the XForm control.
What do you think? Are there any other users that would welcome such a feature?
Thanks,
Mike