This content has been marked as final. Show 3 replies
I should say that I've only tested this in IE/Windows and FF/Windows. It has no effect on FF. (But you could branch around code if the user-agent isn't IE if it bugs you).
I have not tested in other browsers or on other platforms.
Reports of your experience are welcome.
This is actually a fault of IE itself, and is a known issue for a very long time. There are other ways around it, but using the built in datefield isn't one of them. I believe there is a JQuery plugin, with a datefield component, that can bypass this issue. Not positive, but I seem to remember it if you check the plugins page of the JQuery site (jquery.com)
I know it's an IE problem, but the odds of getting Microsoft to fix their bugs is even longer than getting Adobe to fix theirs which itself is as close to zero as to be immeasurable.
I'm not inclined to include yet another package and all its baggage (whatever that might or might not be).
This "RAD" development is becoming considerably less R.