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.
Having a single NavigationPage for the entire CarouselPage creates a plethora of hacks that must be worked around when developing. Simply allowing either a generic Page type or even adding an overload for NavigationPages would be excellent and cut down on the hacks necessary to do many things in Xamarin.Forms.
Thank you for your feature request, we will take your feedback into consideration.