Bug 53215 - Master Details Hamburger Menu Icon not displayed on UWP since V2.3.2.127
Summary: Master Details Hamburger Menu Icon not displayed on UWP since V2.3.2.127
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jimmy [MSFT]
Depends on:
Reported: 2017-03-10 07:22 UTC by Richard Woollcott
Modified: 2017-07-12 12:54 UTC (History)
3 users (show)

See Also:
Tags: bug, uwp, masterdetailpage
Is this bug a regression?: Yes
Last known good build:

Hamburger Menu Icon displayed (25.83 KB, image/png)
2017-03-10 07:22 UTC, Richard Woollcott
Attached IDE logs (1.95 KB, application/x-zip-compressed)
2017-07-12 12:53 UTC, Saurabh Paunikar

Description Richard Woollcott 2017-03-10 07:22:23 UTC
Created attachment 20264 [details]
Hamburger Menu Icon displayed

When using a Master Detail page on UWP Windows 10 Desktop the Hamburger Menu icon is no longer displayed when navigating to a Detail Page.

I am using the Xamarin.Forms MasterDetail Navigation Sample from to identify and reproduce the problem:-

This last worked in Xamarin.Forms V2.3.2.127 - I have attached a screenshot of this showing the Hamburger Icon which is not displayed on the newer versions.

I have tested these versions and all fail:- 

I am using Visual Studio Professional 2015 Update 3 on Windows 10, Version 10.0.14393 Build 14393

Please can you consider this for inclusion in the next release since the Master Detail forms the core navigation of my app and targeting Windows 10 desktop is critical.

Thanks, Richard
Comment 1 Jimmy [MSFT] 2017-03-10 16:38:57 UTC
Thank you for reporting this! I can reproduce the issue with the MasterDetailPage Forms sample and this does appear to be a regression. I am confirming this report so the team can investigate further.

### Regression Test
Forms 2.3.4.-pre4   BAD
Forms     BAD
Forms     GOOD
Comment 2 Jimmy [MSFT] 2017-03-10 16:59:25 UTC
Just as a quick follow up, I tested with a master branch build of Forms and the issue seems resolved due to a change that makes IsPresented intentionally not work in split mode on UWP desktop [1] so the master page is not hidden and there is no need for the menu button.

You can change the MasterBehavior to Popover instead and it will restore similar functionality. This issue doesn't seem to affect the Popover behavior and it works as expected on Forms and 2.3.4-pre4.

[1] https://github.com/xamarin/Xamarin.Forms/pull/707
Comment 3 Richard Woollcott 2017-03-10 19:36:53 UTC
Thanks for the quick response Jimmy much appreciated. I think the bug can be resolved.

So when I changed the sample app to V2.3.4.-pre4 and then edited the MasterDetailPage to explicitly set the MasterBehavior to Popover it worked as you described.

The Sample as presented kinda doesn't really work too well out of the box on UWP with the later versions of Forms since without setting the MasterBehavior the master pane disappears when an item is selected and no hamburger icon is displayed. Explicitly setting the MasterBehaviour to Popover resolves this. And when setting the MasterBehavior to Split an exception is thrown because IsPresented is set in the MainPage OnItemSelected method.

Maybe some comments in the sample source code or ReadMe.MD could help. I appreciate it's probably a bit of a niche scenario.

Comment 4 Jimmy [MSFT] 2017-03-28 17:07:40 UTC
I'll go ahead and resolve this report, and I've created a PR in the samples repo for a workaround in the meantime: https://github.com/xamarin/xamarin-forms-samples/pull/178
Comment 5 Saurabh Paunikar 2017-07-12 12:53:58 UTC
Created attachment 23497 [details]
Attached IDE logs

This issue doesn't exist anymore, hence marking it as Verified

Screencast link : https://www.screencast.com/t/Xdc4mrujR0ok

Environment info : https://gist.github.com/saurabh-paunikar/13e01e9b1600e32a06d2a2528163c77c 

Verfied on

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

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.

Note You need to log in before you can comment on or make changes to this bug.