New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TabbedPage with NavigationPage doesn't behave well on UWP #1627

Closed
HazyFish opened this Issue Jan 21, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@HazyFish

HazyFish commented Jan 21, 2018

Description

When placing a NavigationPage into a TabbedPage, I want to hide the Navigation Bar which appears at the top. However, setting the NavigationPage.HasNavigationBar property to false doesn't work on UWP.

Steps to Reproduce

  1. Create a Tabbed Page with a Navigation Page inside;
  2. Set the NavigationPage.HasNavigationBar to false for the NavigationPage;
  3. Run the UWP App;
  4. Click the Navigation Page tab;
  5. The navigation bar appears.

XAML Code

<?xml version="1.0" encoding="utf-8" ?>
<TabbedPage xmlns="http://xamarin.com/schemas/2014/forms"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             xmlns:local="clr-namespace:TabbedPageWithNavigationPage"
             x:Class="TabbedPageWithNavigationPage.MainPage">

    <local:TodayPage Title="Today"/>
    <NavigationPage Title="Schedule">
        <x:Arguments>
            <local:SchedulePage NavigationPage.HasNavigationBar="False"/>
        </x:Arguments>
    </NavigationPage>

</TabbedPage>

Expected Behavior

The navigation bar should not show up at the top

Actual Behavior

The navigation bar shows up at the top

Basic Information

  • Version with issue: Xamarin.Forms 2.5.0.122203
  • IDE: Visual Studio 2017 Version 15.5.4
  • Platform Target Frameworks:
    • UWP: Windows 10 FCU Build 16299

Screenshots

1

2

@pauldipietro pauldipietro added this to New in Triage Jan 21, 2018

@pauldipietro

This comment has been minimized.

Member

pauldipietro commented Jan 21, 2018

Duplicate of #1437. In the future, do make sure to check if an issue has not already been filed.

@pauldipietro pauldipietro marked this as a duplicate of #1437 Jan 21, 2018

Triage automation moved this from New to Invalid Jan 21, 2018

@samhouts samhouts removed this from Closed in Triage Jun 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment