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.
Use the the WorkingWithListView sample as a starting point. When you run it go to the Context tab. You can swipe left to get context on each row no problem.
Now use the xaml below. This basically wraps the ListView into a TableView. It uses uneven heights and sets the view cell to 300 to give enough room for the list view to display and be scrollable. Now run. The list displays fine. The first swipe for context action works ok. Swipe on second line and it crashes.
<TableView Intent="Form" HasUnevenRows="True">
----existing ListView goes here---
Sorry forgot to mention this is on iOS. I don't have the other platforms to test.
HI Jeff, thank you for taking the time to submit this report. Unfortunately we don't support nested ListtViews on TableViews like this case.
I would suggest to try to layout your UI using different components.
Xamarin Forms Team
Is that documented anywhere? Did I miss that?
I did change over to use a grid yesterday and do it in a more traditional WPF sort of way. That is ok but a few things stuffing me up:
- Lower level views like labels and entry don't support Padding. I am supposed to wrap in a ContentView from what I can see. That means a LOT of additional overhead in setting up the UI.
- Entry boxes don't have border property so I can't get the later iOS standard of no borders on entry boxes.
This stuff can probably be done by getting in and extending the properties and doing renderers and such. However I am not familiar enough with Android/WP to go writing renderers. I just want to build what is a reasonably basic project/tasks app. I am loving the potential in Xamarin forms but man I keep stumbling over little things that are just stopping me all the time.
Hi Jeff, you didn't miss it , it's not properly documented, i passed this info to the docs team.
We are looking in ways to improve how padding and margin will work better.
Thanks for the feedback.