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 for Bug 39414 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
While Xamarin.Forms is intended to follow the native look and feel of the respective platform, you already understand the need to allow developers to customize things through the use of custom renderers. That is why your Xamarin.Forms platform is a HUGE breakthrough! Developers can get so much functionality for free across all platforms, but at the same time, have the power to customize per platform when needed. So I understand that the default rendering of ToolbarItems on iOS uses the default UIBarButtonItem behavior. However, you don’t want Xamarin.Forms to restrict what you could normally do without Xamarin.Forms. iOS allows UIBarButtonItems to take a custom UIView, like a UIButton with an Image on it. Therefore, I think it is critical that Xamarin.Forms introduce a ToolbarItemRenderer so that developers can customize how the UIBarButtonItem is constructed like the underlying iOS platform allows.