I think that the FontSize is intended to propagate to the tab's content, and the perscribed way of setting the header font size is through that light weight style. If so, template binding the font size property to the header would be incorrect.

@StephenLPeters It does not have any effect at all on the Tab's content from what I can see:

<muxc:TabView>
    <muxc:TabView.TabItems>
        <muxc:TabViewItem Header="Tab 1" FontSize="80">
            Some tab content
        </muxc:TabViewItem>
    </muxc:TabView.TabItems>
</muxc:TabView>

I also think if we have the TabViewItem.FontWeight property affecting the TabViewItem's header, so should TabViewItem.FontSize. Anything else would be unexpected API behavior to me. Alternatively, FontWeight. which is currently template bound, should be looked at again.

TabViewItem.FontFamily is inherited for the header:

<muxc:TabView>
    <muxc:TabView.TabItems>
        <muxc:TabViewItem Header="Tab 1" FontFamily="Segoe Script">
            Some tab content
        </muxc:TabViewItem>
    </muxc:TabView.TabItems>
</muxc:TabView>

So from the way I see it - given the current API design - TabViewItem.FontSize should affect the font size of the tab's header - and only that. The way as it stands now, we are currently looking at inconsistent API behavior.

How do you increase the text size in the TabViewItems header? #3047

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions