-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update Flyout when Shell.FlyoutContent changes #17359
Conversation
There is still an issue where removing the value of FlyoutContent the first time will not paint the default flyout text until the window is resized. Adding FlyoutContent always works. A different bug would be needed, or there may already be a bug, such as: |
Ping @PureWeen for review. I think this change is good even if first removing FlyoutContent on WinUI doesn't render the text. That can be solve separately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Can you add tests?
0346e41
to
ed2a168
Compare
@PureWeen, test added |
/backport to release/8.0.1xx-rc2 |
Started backporting to release/8.0.1xx-rc2: https://github.com/dotnet/maui/actions/runs/6628466733 |
/backport to release/8.0.1xx-rc2.1 |
Started backporting to release/8.0.1xx-rc2.1: https://github.com/dotnet/maui/actions/runs/6628705412 |
Description of Change
Shell.FlyoutContent
allows users to change what the Shell's flyout looks like:If
FlyoutContent
changed at runtime, the UI didn't update (either going to custom content, or reverting back to default content when settingFlyoutContent
tonull
).The update functionality was already there, like when
IFlyoutView.Flyout
changed, but that property was also exposed asShell.FlyoutContent
.Issues Fixed
Fixes #9080 (Shell.FlyoutContent does not update with hot reload)