Date Pickers, for Text Controls, format and function a bit differently depending upon where they're used.
On an Android device you don't want the soft keyboard popping up. In a desktop browser you may prefer to have Chrome, Firefox, and Edge behave similarly to each other.
However, the Input Type "Date" is supported in Chrome, but not under Firefox or others.
So... the trick is to use one Textbox Control which will function appropriately within the browser it's running in... and behave nicely under Android.
To do this we must surrender the Alpha built-in Calendar Date Picker and use the jQuery Date Picker. There are lots of themes available and you can create your own if you like.
Attached is an a5w page running a UX Component... which is the criteria established for this process.
There are 4 TextBox Controls... each with slightly different settings. The settings are displayed for each TextBox.
Date 1, 3, and 4 function slightly differently for each browser.
Date 2 responds appropriately under Android... and responds exactly the same under Chrome, Firefox, Edge, and IE.
There are only 2 areas to review within the UX:
onRenderComplete : detects the browser and sets stuff up for Android and Date 2
Javascript function : setDefaultDate() : this tests for each browser and sets default dates where needed. Different formats are required for different browsers.
EDIT: Date 2 has it's property... Custom In-Control Buttons turned on. So have a look in that area for settings and code.
The a5w page was modified slightly from it's default. The jQuery Theme was added.
Testing 5 targets and 4 TextBox controls gets into a "Who's On First" scenario. So if anyone finds something odd... please post.
On an Android device you don't want the soft keyboard popping up. In a desktop browser you may prefer to have Chrome, Firefox, and Edge behave similarly to each other.
However, the Input Type "Date" is supported in Chrome, but not under Firefox or others.
So... the trick is to use one Textbox Control which will function appropriately within the browser it's running in... and behave nicely under Android.
To do this we must surrender the Alpha built-in Calendar Date Picker and use the jQuery Date Picker. There are lots of themes available and you can create your own if you like.
Attached is an a5w page running a UX Component... which is the criteria established for this process.
There are 4 TextBox Controls... each with slightly different settings. The settings are displayed for each TextBox.
Date 1, 3, and 4 function slightly differently for each browser.
Date 2 responds appropriately under Android... and responds exactly the same under Chrome, Firefox, Edge, and IE.
There are only 2 areas to review within the UX:
onRenderComplete : detects the browser and sets stuff up for Android and Date 2
Javascript function : setDefaultDate() : this tests for each browser and sets default dates where needed. Different formats are required for different browsers.
EDIT: Date 2 has it's property... Custom In-Control Buttons turned on. So have a look in that area for settings and code.
The a5w page was modified slightly from it's default. The jQuery Theme was added.
Testing 5 targets and 4 TextBox controls gets into a "Who's On First" scenario. So if anyone finds something odd... please post.
Comment