Ticket #1756 (closed defect: fixed)

Opened 5 months ago

Last modified 4 months ago

DateField time value different from time shown

Reported by: Marko Gronroos Owned by: Marc Englund
Priority: critical Milestone: User Interface Library 5.2.2
Component: undefined Version: 5.2.0
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

The time that the scheduling tries to use can apparently be different from the time shown in the Start date field, as shown in the attached screenshot. I'm not quite sure how this happens, perhaps the time was first set to something earlier and then the date field was used so that the time changed to "current", but this change in time is only shown in the widget and not actually used in the application.

Attachments

tt-scheduletime-20080529.jpg (139.4 kB) - added by Marko Gronroos 5 months ago.
Situation where Start time in UI is different from one tried to use

Change History

Changed 5 months ago by Marko Gronroos

Situation where Start time in UI is different from one tried to use

Changed 5 months ago by Marko Gronroos

  • priority changed from minor to critical
  • version changed from 1.0.0 to 5.2.0
  • component changed from Testing Tools to undefined
  • milestone changed from Testing Tools Backlog to User Interface Library 5.2.1

This is a Toolkit bug, it appears also in Feature Browser.

Changed 5 months ago by Marko Gronroos

  • summary changed from Schedule time different from input to DateField time value different from time shown

Changed 5 months ago by Marc Englund

  • status changed from new to assigned

Might be fixed in [4715], please verify.

If it's still broken, please specify better how to reproduce (how does it appear in FeatureBrowser??)

Changed 4 months ago by Marko Gronroos

Steps how to reproduce. In the Feature Browser, do the following:

  1. Select "Basic value input"
  1. In the "Minute resolution" field, click on the icon to open the calendar, select a date and click on the icon to close the calendar.
  1. Change the time in the input box from keyboard to something else (such as 12:00). When you change focus, the notification shows "12:00:xx" (why are the seconds not zero?), which is correct.
  1. Click on the icon to open the calendar again. The time selectors show the correct time.
  1. Select another date. The time will change to current (is this really desired?), and the new time is also copied in the text box. However, the notification still shows "12:00:xx" as the time. You can click on different dates and the problem remains.
  1. If you change the hour in the popup calendar, while the minutes are something else than what you input in the text field manually, the hour will change properly both in the text field and in the value that is sent to the server, but the minutes will stay the same as what you entered manually. For example, if current time is "15:35" and you change hour to 17, the notification will display "17:00", because you earlier entered "12:00" manually.

Changed 4 months ago by Marko Gronroos

  • owner changed from Marko Gronroos to Marc Englund
  • affects_release_notes unset

I don't think [4715] fixed it. 5.2.1 includes the changeset and still has the problem.

Changed 4 months ago by Marc Englund

  • status changed from assigned to closed
  • resolution set to fixed

Fixed in [4748]

Changed 4 months ago by Marc Englund

  • status changed from closed to reopened
  • resolution deleted

I hear this is still broken, will investigate while looking into #1794

Changed 4 months ago by Marc Englund

  • status changed from reopened to closed
  • resolution set to fixed

Found one more case where this was updated wrong, fixed in [4803]

Note: See TracTickets for help on using tickets.