[ https://issues.apache.org/jira/browse/TRINIDAD-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829976#action_12829976 ]
Matthias Weßendorf commented on TRINIDAD-1384: ---------------------------------------------- this line: if (this.serverOffsetInMins != (void 0)) should be if (this.serverOffsetInMins !== undefined) > Timezones - date picker popup shows a day before > ------------------------------------------------ > > Key: TRINIDAD-1384 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1384 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components > Affects Versions: 1.2.10-core, 1.0.10-core > Environment: Server with timezone set to US Eastern Time (GMT-5), > client browser on a machine with timezone set to > Central European Time (GMT+1) > Reporter: Denis Krukovsky > Priority: Minor > Attachments: DateField.patch > > > Steps to reproduce: > - run a server with timezone set to US Eastern Time (GMT-5). > - Create a page with Trinidad input date and date picker popup. > - Query the page from a browser on a machine with timezone set to Central > European Time (GMT+1). > - Enter some date into input date field. > - Click on datepicker icon. > - Observe that date rendered as selected in datepicker popup is 1 day before > the date entered into inputdate field. > This behavior gets fixed when we edit trinidad-config.xml and include > <time-zone>Etc/GMT-5</time-zone> (server timezone) there. Unfortunately > trinidad-config modification sometimes is not an option because servers and > timezones will change. I tried to supply inputDate component with custom > converter which returns server timezone from getTimeZone() and > getFormattingTimeZone(...) which doesn't help. > I also noted that in both cases - (1) no modification to trinidad-config and > the bug is there, and (2) trinidad-config modified and bug gets fixed - the > Trinidad date picker popup is being requested with equal request string > containing something like > /app/__ADFv__.jsf?_afPfm=-79d68df7&_t=cd&value=1231891200000&loc=en-US&enc=UTF-8, > i. e. the value parameter is same for both cases but datepicker gets > rendered differently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.