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.
Setting the MasterBehavior of a MasterDetailPage to MasterBehavior.SplitOnLandscape is not consistently obeyed on some devices.
The behavior works as expected on an ASUS Transformer Pad (10" tablet) - that is, the Master view operates in Pop-over mode while in portrait, and is permanently split in landscape mode.
However, On an Asus MeMO Pad (8" Tablet, same screen res as Transformer Pad), this behavior is not consistently applied. From my testing, it seems that the behavior works as expected *if the app was started in portrait mode*, however, if the app was started in Landscape mode, the the popover behavior is applied in both screen orientations.
Can you check if the DeviceIdiom you get is the same for both devices.
Hi, sorry for the delayed response.
The larger device is correctly reported as a Tablet. The smaller device is being reported as a Phone (even though it most certainly is a tablet!).
How are devices assigned idioms? Regardless of whether you class the device as a tablet/phone, the behavior varying according to start-up orientation seems to be a bug.
What version of XF are you usin?
Can you try the latest prerelease and see what's the DeviceIdiom reported ?
I'll give that a go, and get back to you tomorrow morning (GMT+1).
This seems to be fixed with the latest version of XF 184.108.40.20687 (the full, non-prerelease version was released after your comment), so this issue can now be closed.
Thank you @Joseph for the confirmation.
As per comment 5, I am marking this issue as VERIFIED-FIXED.