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 7512 [details]
On Android and Winphone, when displaying an ActionSheet, using DisplayActionSheet(...), if there are buttons that do not fit on screen, there is no way to select them. On iOS you can scroll to the off-screen buttons, but on WinPhone and Android you can not.
1. Load attached test project
2. Set either Android or WinPhone project as startup project and run app.
3. Press the Display ActionSheet button
Expected result: should be able to select any of the 14 extra buttons.
Actual result: can only select the buttons that are displayed on screen, can not scroll down to access other buttons.
If you run the iOS project, you will see that you can scroll and select any of the 14 extra action buttons.
Can the priority of this be increased please? This defect makes DisplayActionSheet unfit for purpose for any more than a handful of buttons, as there is no guarantee that the user is not on a small device. Even on my Nokia Lumia phone, in landscape orientation I can only see 5 (sometimes 6) items.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team