Bug 38443 - ListView LayoutChange event with incorrect Args
Summary: ListView LayoutChange event with incorrect Args
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-02-04 11:50 UTC by s.delestre
Modified: 2016-12-20 23:04 UTC (History)
2 users (show)

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 s.delestre 2016-02-04 11:50:36 UTC
When you attach the LayoutChange event of a ListView, when it's fired, in the LayoutChangeEventArgs, the e.OldRight e.Right are not availables.

Moreover it's typed as a simple EventArgs (instead of a LayoutChangeEventArgs) that could explains the fact that the properties was not correctly set.

Best regards,
Comment 1 adrianknight89 2016-11-26 22:24:07 UTC
There is no LayoutChanged in ListView. Did you mean a layout instead? That's Core. 

If you mean Android native, it's different. Can you attach a repro so we can visualize what you mean?
Comment 2 Rui Marinho 2016-12-20 23:04:38 UTC
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.

Warm regards, 
Xamarin Forms Team