This question is locked. New answers and comments are not allowed.
Hi,
I started to use the html date picker (ver 2013.1.417) on our project and ran into several issues.
I think they are fatal flaws and will force us to have to use something else like the MS Win8 SDK datepicker.
It would be great if I'm wrong, so:
1. Can I have the control initialized with certain dates disabled? In most of my scenarios, my customers can only select weekdays (and then I also have some custom weekdays that are unavailable, i.e. company holidays)
2. The biggest issue it seems is validation. This control really needs to tie into html5/windows store form validation.
I need this picker to be able to have properties such as ".required" & ".setCustomValidity".
It needs to tie into a form when I ask the submit event if "event.target.checkValidity()" is valid or not.
And it needs to tie into the built in form input styles.
Any thoughts or insights are appreciated.
(or send these thoughts on to the dev team for consideration for a future release.)
Thanks,
Randy
I started to use the html date picker (ver 2013.1.417) on our project and ran into several issues.
I think they are fatal flaws and will force us to have to use something else like the MS Win8 SDK datepicker.
It would be great if I'm wrong, so:
1. Can I have the control initialized with certain dates disabled? In most of my scenarios, my customers can only select weekdays (and then I also have some custom weekdays that are unavailable, i.e. company holidays)
2. The biggest issue it seems is validation. This control really needs to tie into html5/windows store form validation.
I need this picker to be able to have properties such as ".required" & ".setCustomValidity".
It needs to tie into a form when I ask the submit event if "event.target.checkValidity()" is valid or not.
And it needs to tie into the built in form input styles.
#elementname input:valid {}#elementname input:invalid { border:solid red; font-weight:bold;}#elementname input:required{}#elementname input:optional{} Any thoughts or insights are appreciated.
(or send these thoughts on to the dev team for consideration for a future release.)
Thanks,
Randy