Hold on, I’ve just realised that it can display the next day *before* it’s 
submitted. Maybe it *is* a bug. Unfortunately I can’t spend any time on it at 
the moment.

Note too that option (c) can’t control what day DateField thinks is *today*. 
DateField relies on the client’s timezone setting for that. An improvement to 
DateField might be a timezone parameter.

> On 10 Jul 2015, at 11:32 am, Geoff Callender 
> <geoff.callender.jumpst...@gmail.com> wrote:
> 
> It’s confusing, but it’s not really a bug. What you’re seeing is the 
> date-time redisplayed to you in the server timezone, which is Australian 
> Eastern Standard Time. In the Submitted Value column you’ll see the date-time 
> shows timezone “EST”.
> 
> HTTP requests don’t include timezone, so either (a) the server has to assume 
> you’re in its timezone; or (b) use JavaScript to detect your timezone and 
> pass it through in the submit; or (c) get the user to nominate the timezone 
> they want to see (iCloud’s web interface does it the latter way). In my own 
> software I usually go with (c) because it lets a traveller choose the 
> timezone that they want to think in.
> 
> As for the JumpStart example, I think I'll modify it to include a timezone 
> selector. That way there’ll be no confusion.
> 
> See also this unresolved issue: 
> https://issues.apache.org/jira/browse/TAP5-841 .
> 
>> On Jul 8, 2015, at 2:18 AM, Sumanth <roasteddra...@gmail.com> wrote:
>> 
>> Hello Everyone
>> 
>> is anyone able to verify that is this a bug or not? If it is can anyone
>> let us know when can we see a fix for this?
>> 
>> Or is my details too short? Should I need to include anything else. Please
>> let us know. How can we work around this!
>> 
>> On Fri, Jun 19, 2015 at 11:16 AM, Sumanth <roasteddra...@gmail.com> wrote:
>> 
>>> Hi all,
>>> To reproduce this.
>>> 
>>> Currently my timezone is (UTC+1) Amsterdam,berlin etc and I'm living in
>>> this time zone.. And i change my system/OS(Windows) time zone to (UTC -5 )
>>> Eastren Time (US & Canada).
>>> 
>>> Then go to the jumpstart's website
>>> 
>>> http://jumpstart.doublenegative.com.au/jumpstart7/examples/component/coreinputcomponents
>>> 
>>> and select any date . The date that appears on the date field gets added
>>> +1 day
>>> 
>>> for eg : selected date - 01/06/2015 (dd/mm/yyyy)
>>>          displayed date - 02/06/2015 (dd/mm/yyyy)
>>>          expected date - 01/06/2015 (dd/mm/yyyy).
>>> 
>>> 
>>> Also noticed was, the time selected in milliseconds was showing 10:00 PM
>>> in the night while this was being done at 10:00 in the morning, the time
>>> difference between GMT and CEST is 2hr so adding this to 10:00 PM it is
>>> next day.
>>> 
>>> I hope this helps, but do let us know if this is the way it should behave
>>> as from user perspective, if I'm selecting 01/06 i would like to 01/06  no
>>> matter where I am from.
>>> 
>>> Thanks in advance,
>>> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to