Closed gregh3269 closed 10 years ago
Ok, found out the reason, the type now needs to be type="text" rather than type="date". Must have changed in the release.
eg <..> input name="eventDateString" id="eventDateString" type="text" value="15/11/14" data-role="datebox" data-options='{"mode": "calbox", "themeHeader" : "b", "useNewStyle":true, "useFocus":true, "overrideDateFormat": "%d/%m/%y", "beforeToday": true, "minDays" : 4.0 }' readonly="readonly" data-inline="true"
Cheers Greg
Well, yes. Sometimes at least. It totally depends on the browser.
Here's what happens:
Case 1.) (most browsers) - DateBox initializes the input element, and when it runs, it changes the type to text.
Case 2.) (some browsers) - DateBox initializes, tries to change the element type, and dies when the browser won't let it.
I believe at this point all of the demos show type="text" - type="date" will only allow the browser dependant date format in it (assuming that type="date" is supported). Long story short, the fix of just using "text" instead is way easier (and as far as I can tell always works)
Hello,
The calbox date does not seem to show on chrome 35.0.1916.138. The widget shows but there is nothing inside the box. The pop works ok but does not return anything.
datebox 1.4.4 jqm 1.4.5 jquery-1.11.1
here is what I am using: <..> input name="eventDateString" id="eventDateString" type="date" value="15/11/14" data-role="datebox" data-options='{"mode": "calbox", "themeHeader" : "b", "useNewStyle":true, "useFocus":true, "overrideDateFormat": "%d/%m/%y", "beforeToday": true, "minDays" : 4.0 }' readonly="readonly" data-inline="true"
It works OK with the useragent switcher on ff 31.2.0.
Any ideas?
Cheers Greg