Bug 60513 - [MacOS] TimePicker raises PropertyChanged before it changes Time
Summary: [MacOS] TimePicker raises PropertyChanged before it changes Time
Status: ASSIGNED
Alias: None
Product: Forms
Classification: Xamarin
Component: Mac ()
Version: 2.5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Rui Marinho
URL:
Depends on:
Blocks:
 
Reported: 2017-11-03 12:27 UTC by Michael Rumpler
Modified: 2017-11-03 17:13 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 60513 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
ASSIGNED

Description Michael Rumpler 2017-11-03 12:27:23 UTC
When the user changes the time of a TimePicker, then the PropertyChanged event is raised, but the Time property still holds the old value. The event should be raised AFTER the value has changed.

I tested this in XF 2.5.0.19271-pre2 on MacOS.

The repro project from bug 60510 also demonstrates this issue. https://bugzilla.xamarin.com/attachment.cgi?id=25552