Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0027510
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2014-08-29 15:252014-09-03 15:27
ReportercaristuView Statuspublic 
Assigned ToAugustoMauch 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version3.0PR14Q4
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0027510: Absolute Time is not displaying the absolute time when the timezone changes

DescriptionAbsolute 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.
Steps To Reproduce1) 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)
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00276363.0PR14Q4 closedAugustoMauch Absolute Date Time fields are not handling properly DST changes of the timezone 

-  Notes
(0069947)
AugustoMauch (manager)
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.

- Issue History
Date Modified Username Field Change
2014-08-29 15:25 caristu New Issue
2014-08-29 15:25 caristu Assigned To => AugustoMauch
2014-08-29 15:25 caristu Modules => Core
2014-08-29 15:25 caristu Resolution time => 1411768800
2014-08-29 15:25 caristu Triggers an Emergency Pack => No
2014-08-29 15:25 caristu version => pi
2014-08-29 15:32 caristu Description Updated View Revisions
2014-08-29 15:33 caristu Issue Monitored: networkb
2014-09-03 15:27 AugustoMauch Note Added: 0069947
2014-09-03 15:27 AugustoMauch Status new => closed
2014-09-03 15:27 AugustoMauch Resolution open => no change required
2014-09-18 12:56 caristu Relationship added related to 0027636


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker