Ticket #1794 (closed defect: fixed)
DateField server/client time mixup
| Reported by: | Marc Englund | Owned by: | Marc Englund |
|---|---|---|---|
| Priority: | major | Milestone: | User Interface Library 5.2.3 |
| Component: | undefined | Version: | |
| Keywords: | Cc: | ||
| Known Issue description: | |||
| Hours estimate: | Deadline (dd.mm.yyyy): | ||
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | no | Contract: | |
Description
If a datefield is null on the server, it's presented to the user with the current client time. If the user selects date (and not time), only the date is sent to the server, but the server and client may have a different idea of 'current time' -> the server has a different time than is shown on the client.
If the datefield was null, all variables must be sent, so that the server and client agree on the time.
(Can be reproduced by setting a different time on the server and client, and trying FeatureBrowser?->BasicInput?)
Change History
Note: See
TracTickets for help on using
tickets.
