Skip to content
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

[Fix proposed] TabView bottom border line is too short #5954

Closed
eugenegff opened this issue Sep 24, 2021 · 8 comments · Fixed by #5981 or #6282
Closed

[Fix proposed] TabView bottom border line is too short #5954

eugenegff opened this issue Sep 24, 2021 · 8 comments · Fixed by #5981 or #6282
Labels
area-TabView team-Controls Issue for the Controls team

Comments

@eugenegff
Copy link
Contributor

Describe the bug
TabView bottom border line is too short in new styles

Screenshots
image

@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Sep 24, 2021
eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 24, 2021
@ghost ghost added the working on it label Sep 24, 2021
@eugenegff
Copy link
Contributor Author

Note, that in styles v1 shadow had Grid.ColumnSpan="4", covering LeftContentColumn, TabColumn, AddButtonColumn, RightContentColumn, but in Win11 like styles separator line covers only TabColumn and AddButtonColumn - seems to be simply overlooked

@eugenegff eugenegff changed the title TabView bottom border line is too short [Fix proposed] TabView bottom border line is too short Sep 24, 2021
@ghost ghost removed the working on it label Sep 27, 2021
eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 27, 2021
@ghost ghost added the working on it label Sep 27, 2021
@beervoley
Copy link
Contributor

beervoley commented Sep 27, 2021

@eugenegff I believe in this case it's caused by having custom content it TabView Footer.
If this is the case, it was done on purpose so users can customize that region without having to be locked in with the provided border. If you need to extend the border in this case, please use TabViewBorderBrush for the bottom border of the footer :)

@eugenegff
Copy link
Contributor Author

eugenegff commented Sep 27, 2021

@eugenegff I believe in this case it's caused by having custom content it TabView Footer.
If this is the case, it was done on purpose so users can customize that region without having to be locked in with the provided border. If you need to extend the border in this case, please use TabViewBorderBrush for the bottom border of the footer :)

That TabView is extended into TitleBar as in https://docs.microsoft.com/en-us/windows/apps/design/controls/tab-view sample, there are

                    <muxc:TabView.TabStripHeader>
                        <Grid x:Name="ShellTitlebarInset" Background="Transparent" />
                    </muxc:TabView.TabStripHeader>
                    <muxc:TabView.TabStripFooter>
                        <Grid x:Name="CustomDragRegion" Background="Transparent" />
                    </muxc:TabView.TabStripFooter>

If you insist that such non-intuitive and not backward compatible behavior is by design - then sample should probably be fixed.

Note, that XamlControlsGallery has many samples of TabView without TabStripFooter - all with this visual glitch. It actually forces us to always create TabStripFooter to fix it - and it is not good. OTOH, (rare?) applications that does not want this stroke at TabStripFooter can always hide it under opaque TabStripFooter or override TabViewBorderBrush

image

Here is screenshot of released app that uses WinUI 2.6 that shows that this visual glitch is regression - WinUI 2.6 has shadow at this place instead of the stroke line, and shadow extends on whole window width

image

@beervoley
Copy link
Contributor

beervoley commented Sep 27, 2021

@eugenegff I believe in this case it's caused by having custom content it TabView Footer.
If this is the case, it was done on purpose so users can customize that region without having to be locked in with the provided border. If you need to extend the border in this case, please use TabViewBorderBrush for the bottom border of the footer :)

That TabView is extended into TitleBar as in https://docs.microsoft.com/en-us/windows/apps/design/controls/tab-view sample, there are

                    <muxc:TabView.TabStripHeader>
                        <Grid x:Name="ShellTitlebarInset" Background="Transparent" />
                    </muxc:TabView.TabStripHeader>
                    <muxc:TabView.TabStripFooter>
                        <Grid x:Name="CustomDragRegion" Background="Transparent" />
                    </muxc:TabView.TabStripFooter>

If you insist that such non-intuitive and not backward compatible behavior is by design - then sample should probably be fixed.

Note, that XamlControlsGallery has many samples of TabView without TabStripFooter - all with this visual glitch. It actually forces us to always create TabStripFooter to fix it - and it is not good. OTOH, (rare?) applications that does not want this stroke at TabStripFooter can always hide it under opaque TabStripFooter or override TabViewBorderBrush

Here is screenshot of released app that uses WinUI 2.6 that shows that this visual glitch is regression - WinUI 2.6 has shadow at this place instead of the stroke line, and shadow extends on whole window width

I see now. Yes, you're right - it's not very intuitive and it definitely should span the entire width. :)

eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 28, 2021
eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 28, 2021
eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 28, 2021
(cherry picked from commit 1c697fe)
(cherry picked from commit 4fa9f08)
@ranjeshj ranjeshj added area-TabView team-Controls Issue for the Controls team and removed needs-triage Issue needs to be triaged by the area owners labels Sep 29, 2021
eugenegff added a commit to eugenegff/microsoft-ui-xaml that referenced this issue Sep 30, 2021
(cherry picked from commit 1c697fe)
(cherry picked from commit 4fa9f08)
@ghost ghost removed the working on it label Oct 1, 2021
@ghost ghost added the working on it label Nov 11, 2021
@ghost ghost removed the working on it label Nov 18, 2021
@ghost
Copy link

ghost commented Apr 14, 2022

🎉This issue was addressed in #5981, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 13, 2022

🎉This issue was addressed in #5981, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

@ghost
Copy link

ghost commented Jul 18, 2022

🎉This issue was addressed in #5981, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

@ghost
Copy link

ghost commented Jan 3, 2023

🎉This issue was addressed in #5981, which has now been successfully released as Microsoft.UI.Xaml v2.8.2.:tada:

Handy links:

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