Bug 39971 - Windows Phone Settting IsVisible is ignored whilst FadeTo is running
Summary: Windows Phone Settting IsVisible is ignored whilst FadeTo is running
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.1.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Rui Marinho
URL:
Depends on:
Blocks:
 
Reported: 2016-03-29 17:52 UTC by Jonck
Modified: 2017-06-16 21:23 UTC (History)
4 users (show)

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


Attachments
Repro code (1003 bytes, text/plain)
2016-03-29 17:52 UTC, Jonck
Details


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 on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Jonck 2016-03-29 17:52:25 UTC
Created attachment 15545 [details]
Repro code

As the title says, If you run the FadeTo animation on a visual element and set the IsVisible property on it whilst (or very close after) the animation is running it will be ignored.

I have attached some repro code.
Comment 1 Paul DiPietro [MSFT] 2017-06-16 21:23:15 UTC
Running on the latest 2.3.6 nightly build the behavior looks to be the same with or without the await statement. As such this will be closed. If this is in error and/or the issue appears to be appearing in some particular form, please reopen with an up to date reproduction project.