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.
If you access the main page as a tabbed page - which you can via something like:
var x = Application.Current.MainPage as TabbedPage;
The isEnabled property is available from each of the children, as is the isVisible property.
x.Children.isEnabled = false;
This to my mind would disable the first tab, but it does nothing, as does isVisible.
If I use a custom renderer, then I can probably disable tabs on the first run, but since everything in my app is based upon a tabbed page, they will never refresh, so will be permanently disabled.
There should be a way of modifying tabs in the above method or similar, some kind of override, without the need for a custom renderer - since the tabbed page is often only rendered once.
I tried to reproduce this issue but not sure about the steps, that result unable to reproduce this.
Could you please share a small sample application that demonstrate this issue. That would be very helpful to reproduce this issue at our end.
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.
Xamarin Forms Team