Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 17024 [details]
Images with the problem, Test solution and all info about my Xamarin install
I needed to create a sticky header for a AbsoluteLayout view which is in ScrollView....
So I added another element to the view and decided I would change the new elements Layout bounds property like so
`element.SetValue(AbsoluteLayout.LayoutBoundsProperty, new Rectangle(0, y, this.Width, calculatedHeight))`
This approach works fine on our iOS devices, but on Android after some massive flinging it just wont move around anymore! If I am looking at elements properties I see that the Y value changes, but it just wont move to the new position.....
To visualise the problem I have attached images with a complete test code.....
It appears that the issue is present on Android devices running Android 4.2.2 to 5.0
I was unable to reproduce the behavior on my Android 5.0 device, nor on any emulators. Can you be more specific about "massive flinging" and/or the particular devices that you're testing on?
I do see the header move down, but it always goes back to the top where it is supposed to be.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!