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

ProgressRing disappears within a CommandBar when items go to the overflow list and back again #4636

Closed
jp-weber opened this issue Mar 23, 2021 · 2 comments
Labels
area-Progress ProgressBar, ProgressRing no-issue-activity team-Controls Issue for the Controls team

Comments

@jp-weber
Copy link
Contributor

jp-weber commented Mar 23, 2021

Describe the bug
If the width of the window is changed and items are displayed in the overflow list of the CommandBar, this will cause the ProgressRing to disappear when the width of the window is increased again and the items are displayed in the normal list again.

Example XAML

    <CommandBar OverflowButtonVisibility="Auto">
        <CommandBar.PrimaryCommands>
            <AppBarElementContainer>
                <Grid>
                    <muxc:ProgressRing
                                Value="23" 
                                Maximum="30" 
                                Width="40"
                                Height="40"
                                IsIndeterminate="False"/>
                    <TextBlock 
                                Opacity="0.6"
                                Text="23"
                                FontSize="12"
                                VerticalAlignment="Center" 
                                HorizontalAlignment="Center"/>
                </Grid>
            </AppBarElementContainer>
            <AppBarButton Icon="Accept"/>
            <AppBarButton Icon="Add"/>
            <AppBarButton Icon="Account"/>
            <AppBarButton Icon="DockBottom"/>
            <AppBarButton Icon="DisconnectDrive"/>
            <AppBarButton Icon="Favorite"/>
            <AppBarButton Icon="Folder"/>
        </CommandBar.PrimaryCommands>
    </CommandBar>

Steps to reproduce the bug

Steps to reproduce the behavior:

  1. Copy the example code to your app
  2. Change the width of the app to min and back again
  3. see the error

Expected behavior

Screenshots
enough width
grafik

overflow list
grafik

all items in the normal list again
grafik

Version Info

NuGet package version: Microsoft.UI.Xaml 2.6.0-prerelease.210315002

Windows app type:

UWP Win32
Yes Yes
Windows 10 version Saw the problem?
Insider Build (xxxxx)
October 2020 Update (19042) Yes
May 2020 Update (19041)
November 2019 Update (18363)
May 2019 Update (18362)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)
Device form factor Saw the problem?
Desktop Yes
Xbox
Surface Hub
IoT

Additional context

@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Mar 23, 2021
@ranjeshj ranjeshj added area-Progress ProgressBar, ProgressRing team-Controls Issue for the Controls team and removed needs-triage Issue needs to be triaged by the area owners labels Mar 23, 2021
@ranjeshj
Copy link
Contributor

Looks like AppBarElementContainer might be moving its children based on overflow which is messing with ProgressRing rendering.

@jp-weber jp-weber changed the title ProgressRing disappears within a CommandBar when items go to the overflow list and back again (WinUi2) ProgressRing disappears within a CommandBar when items go to the overflow list and back again Jan 23, 2022
@github-actions
Copy link

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Progress ProgressBar, ProgressRing no-issue-activity team-Controls Issue for the Controls team
Projects
None yet
Development

No branches or pull requests

2 participants