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.
Well when I call TranslateTo an scrollview on Xamarin.Forms, it's both ScrollX and ScrollY becomes 0.
yes - any invalidate does it. It makes this control utterly unusable. I even tried working around it with custom renderers; but like most forms code, you guys seal/hide the members necessary to do so.
This therefore needs to be fixed - there is no workaround.
Actually there is a workaround. Someone from SO suggested it. Put the scrollview inside a contentview than translate the contentview. Scroll indexes won't be becoming 0 anymore.
Unfortunately that workaround does not work for other cases where it occurs such as the size of the scrollview changing.
Similar to: https://bugzilla.xamarin.com/show_bug.cgi?id=43947
Is there an update on a fix for this issue?
Created attachment 24466 [details]
scrollview demo page
I'm not able to reproduce this on 220.127.116.119-pre2.
Created attachment 24467 [details]
scrollview demo page
Apologies, I wasn't using TranslateTo. I see now it changes ScrollX/ScrollY to 0.
This appears to be iOS. Android behaves properly.
Hi David. Any update on this issue?
I can still reproduce it on 18.104.22.1680. Suggested workaround doesn`t work for me. Thanks
Please follow the issue on GitHub for updates. Thanks!