Bug 28474 - Visual bug on Windows Phone's TabbedPage Title
Summary: Visual bug on Windows Phone's TabbedPage Title
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-03-26 14:59 UTC by Sergiu
Modified: 2015-05-20 21:17 UTC (History)
3 users (show)

Tags: windows visual tabbedpage
Is this bug a regression?: ---
Last known good build:


Attachments
visual error with one tab (33.52 KB, image/jpeg)
2015-03-26 14:59 UTC, Sergiu
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Sergiu 2015-03-26 14:59:07 UTC
Created attachment 10521 [details]
visual error with one tab

this is the code I am using

<TabbedPage xmlns="http://xamarin.com/schemas/2014/forms"
            xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
            x:Class="RATBVFormsX.Views.BusStationsView"
            Title="Bus Stations">
  <TabbedPage.Children>
    <ContentPage Title="{Binding BusLineName}">
      <ListView ItemsSource="{Binding BusStations}"
                ItemSelected="BusStation_OnItemSelected">
        <ListView.ItemTemplate>
          <DataTemplate>
            <ViewCell>
              <StackLayout Orientation="Vertical">
                <Label FontAttributes="Bold" HorizontalOptions="FillAndExpand"
                       Text="{Binding Name}"/>
              </StackLayout>
            </ViewCell>
          </DataTemplate>
        </ListView.ItemTemplate>
      </ListView>
      <ContentPage.ToolbarItems>
        <ToolbarItem Name="Tour" Order="Primary" Priority="0">
          <ToolbarItem.Icon>
            <OnPlatform x:TypeArguments="FileImageSource"
                        WinPhone="Assets/reverse.png"
                        Android="ic_action_return.png"
                        iOS="Return.png"/>
          </ToolbarItem.Icon>
        </ToolbarItem>
        <ToolbarItem Name="Download" Order="Primary" Priority="1">
          <ToolbarItem.Icon>
            <OnPlatform x:TypeArguments="FileImageSource"
                        WinPhone="Assets/download.png"
                        Android="ic_action_download.png"
                        iOS="Download.png"/>
          </ToolbarItem.Icon>
        </ToolbarItem>
      </ContentPage.ToolbarItems>
    </ContentPage>
  </TabbedPage.Children>
</TabbedPage>

but I get the visual error you see in the attached file, from what I can determine it is because of the Binding in the title text property, if I remove it and place normal text it is OK, also if I add another tab it overlays badly, I also have to mention this is the 2nd page in the app, if I click a name in the list and go to the 3rd page and then back then everything is OK, but if I go to the 1st page and then back to 2nd again I see this visual error again

I tested on Android phone and simulator and also on a iOS simulator and it only happens on windows phone
Comment 1 Jason Smith [MSFT] 2015-05-18 16:31:22 UTC
Can you please provide the view model or a view model that reproduces this issue?
Comment 2 Sergiu 2015-05-20 21:17:08 UTC
apparently, I cannot reproduce it anymore, I am running the latest version so I think it has been fixed, if I see it again I will report it

thank you