Unfortunately modernizer does not really support that. From the docs

Modernizr cannot detect that date inputs create a datepicker,

It is possible to detect if a browser support type="date" but that does not
mean it has a datepicker. I suspect I'm going to add an option to give it a
try.


On Thu, Oct 3, 2013 at 8:12 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:

> Sounds good, Barry.
>
> You mentioned earlier that you were "planing on using modernizr to detect
> if type="date" is supported. " so that browsers with good HTML5 date
> support (eg. iOS Safari, Chrome) are left alone. How did that go?
>
>
> On 3 October 2013 12:08, Barry Books <trs...@gmail.com> wrote:
>
> > I've uploaded the initial version to github
> >
> > https://github.com/trsvax/tapestry-datepicker
> >
> > I think I'm going to make this standalone project that only contains the
> > datepicker. This will make it easier for other project to just include
> it.
> > Currently to use it you will have to download and build it.  Here is an
> > example usage
> >
> > <t:form>
> >     <t:textfield value="date" t:mixins="datefield/JQueryDatePicker"
> > data-duration="slow"/>
> >     <input type="submit"/>
> >   </t:form>
> >
> >
> > All that's required is the input type be a date which causes Tapestry to
> > use a Date Translator to convert the data to/from a string. This also
> > creates the client side validation. The mixin adds the client side
> > interface. In this case the JQuery UI calendar.
> >
> > If you prefer you can create your own component and override the Tapestry
> > one.
> >
> > public class DateField extends TextField {
> >
> >     @Mixin
> >     private JQueryDatePIcker mixin;
> >
> > }
> >
> > Questions, commets etc are welcome
> >
> > Barry
> >
>

Reply via email to