Bug 39506 - Effects.Clear does not detach the effect.
Summary: Effects.Clear does not detach the effect.
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.1.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-10 02:28 UTC by Mark Smith
Modified: 2016-04-26 18:52 UTC (History)
5 users (show)

Tags: ac
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 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:

Description Mark Smith 2016-03-10 02:28:43 UTC
# Steps to reproduce
1. Create a new Xamarin.Forms app w/ X.F. 2.1
2. Add an effect to an element
3. Call Clear() on the Effects collection on the element

# Expected behavior
Expected OnDetach to be called.

# Actual behavior
No detach was invoked.

# Supplemental info (logs, images, videos)

# Test environment (full version information)
Comment 1 Jason Smith [MSFT] 2016-03-25 23:17:50 UTC
Should be fixed in 2.2.0-pre1
Comment 2 Parmendra Kumar 2016-04-26 18:46:08 UTC
To verify this issue I have tried to reproduce this issue but I am not able to reproduce this issue.

Could you please provide me some code snap? so that I can verify this issue efficiently.

Comment 3 Mark Smith 2016-04-26 18:52:32 UTC
I think it's been fixed, it's working correctly for me.