-
Notifications
You must be signed in to change notification settings - Fork 315
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
Dashboard not refreshing when removing widgets #3360
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
I was able to reproduce this as well, it is a refresh issue, the widgets are being removed and are not active after removal. |
Dev Home version
0.1501.547.0
Windows build number
10.0.22621.3737
Other software
OS Build Version: 10.0.22621.3737.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.6
Steps to reproduce the bug
Add a widget to dashboard and remove it. It will stay in the dashboard but in a frozen state. Navigate out of dashboard page and navigate back to it to see it actually removed.
Expected result
Widgets removed should not be shown in dashboard.
Actual result
Widgets stay in the dashboard in a frozen state after being removed. It is needed to navigate away from dashboard page to see the changes in UI.
Included System Information
No response
Included Extensions Information
Extensions:
Microsoft.DevHomeMicrosoftGameDevExtension_0.400.536.0_x64__8wekyb3d8bbwe (Dev Home Microsoft Game Dev Extension (Preview))
Microsoft.Windows.DevHome.Canary_0.1501.547.0_x64__8wekyb3d8bbwe (Core Widget Extension)
Microsoft.Windows.DevHome.Canary_0.1501.547.0_x64__8wekyb3d8bbwe (Hyper-V Extension)
Microsoft.Windows.DevHomeAzureExtension.Canary_0.1000.549.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Canary))
Widget Service:
MicrosoftWindows.Client.WebExperience_524.13200.30.0_x64__cw5n1h2txyewy
The text was updated successfully, but these errors were encountered: