I will look for it later - I'm a little tied up right now.
-Adrian
David E Jones wrote:
I looked around and don't see a jira issue for it. Here are the search results
I'm basing that on:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&query=calendar&summary=true&description=true&body=true&pid=12310500&status=1&status=3&status=4
I could be missing something though...
-David
On Mar 25, 2010, at 3:01 PM, Adrian Crum wrote:
There is a Jira issue somewhere. I remember suggesting that we should serve the
calendar popup from the server (like we do with lookup windows) to solve those
issues.
-Adrian
David E Jones wrote:
There are a couple of issues with the current calendar popup script we're using:
1. AM/PM issue: the PM doesn't get passed to the server, so for example if you
select 2:00 PM in the calendar the server gets 02:00 and interprets that as
2:00 AM
2. time zone issue: the calendar uses the time zone of the browser, which may
be different from the user's time zone setting on the server; if this is the
case the time actually saved will be wrong by the difference between the
browser's time zone offset and the user's time zone offset (or server's if no
user setting)
Has anyone run into these issues and/or looked into fixing them?
My first intent is to see if there are parameters we can pass to the current
calendar script to see if we can continue using it, and if not then to look for
yet another new calendar script (we've had a few over the years... :( ).
-David
