Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0027510Openbravo ERPA. Platformpublic2014-08-29 15:252014-09-03 15:27
caristu 
AugustoMauch 
urgentmajoralways
closedno change required 
5
pi 
3.0PR14Q4 
Core
No
0027510: Absolute Time is not displaying the absolute time when the timezone changes
Absolute Time is not displaying the absolute time when the timezone changes. This situation can happen only in very specific cases, for example, when working with the application the moment when the time changes to the summer.
1) Take a field that uses the Absolute Time reference
2) Save a time, for example 19:00.
3) Change the computer timezone, for example one hour less
4) Refresh the window, notice that it is showing 18:00
5) Log-out and log-in, now the field shows the correct time (19:00)
No tags attached.
related to defect 00276363.0PR14Q4 closed AugustoMauch Absolute Date Time fields are not handling properly DST changes of the timezone 
Issue History
2014-08-29 15:25caristuNew Issue
2014-08-29 15:25caristuAssigned To => AugustoMauch
2014-08-29 15:25caristuModules => Core
2014-08-29 15:25caristuResolution time => 1411768800
2014-08-29 15:25caristuTriggers an Emergency Pack => No
2014-08-29 15:25caristuversion => pi
2014-08-29 15:32caristuDescription Updatedbug_revision_view_page.php?rev_id=6500#r6500
2014-08-29 15:33caristuIssue Monitored: networkb
2014-09-03 15:27AugustoMauchNote Added: 0069947
2014-09-03 15:27AugustoMauchStatusnew => closed
2014-09-03 15:27AugustoMauchResolutionopen => no change required
2014-09-18 12:56caristuRelationship addedrelated to 0027636

Notes
(0069947)
AugustoMauch   
2014-09-03 15:27   
This is a browser issue, nothing can be done from the Openbravo code to fix it. We have tested it in two machines, in one it was reproducible, in the other was it was not.

Behaviour when it was not reproducible:
  After changing the timezone, we executed new Date() and isc.Time.UTCHoursDisplayOffset. The new date timezone offset was the same as the UTCHoursDisplayOffset. Neither of them were actually updated to the new timezone, but they were coherent between them, so the absolute time worked.


Behaviour when it was not reproducible:
  After changing the timezone, we executed new Date() and isc.Time.UTCHoursDisplayOffset. The new date timezone offset was updated, but UTCHoursDisplayOffset showed the previous timezone offset. The discrepancy results in a time not shown in absolute format. When this happens, reloading the window (F5) solved the problem.