-
Notifications
You must be signed in to change notification settings - Fork 760
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: Fix DataContext lost on second HR on Android #19524
Conversation
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19524/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19524/index.html |
@Mergifyio backport release/stable/5.6 |
✅ Backports have been created
|
src/Uno.UI.RemoteControl/HotReload/ClientHotReloadProcessor.Common.cs
Outdated
Show resolved
Hide resolved
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19524/index.html |
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19524/index.html |
|
The build 155100 found UI Test snapshots differences: Details
|
…5.6/pr-19524 fix: Fix DataContext lost on second HR on Android (backport #19524)
closes https://github.com/unoplatform/private/issues/611
closes https://github.com/unoplatform/private/issues/612
closes https://github.com/unoplatform/private/issues/617
closes https://github.com/unoplatform/private/issues/624
closes https://github.com/unoplatform/private/issues/645
Bugfix
Fix
DataContext
lost on second HR on AndroidWhat is the current behavior?
As
Frame
does not allow easy update ofContent
, on HR we inject new instance (Page_v2
) asContent
of previous instance (Page_v1
). We also flushDataContext
ofPage_v1
to make sure 2-way bindings are no longer triggered.The issue is that on second HR (
Page_v3
) as thePage_v1
is still present in the tree, it matches (novelty of HR w/o cnomua) and is being used to clone properties toPage_v3
, driving to clone an emptyDataContext
.What is the new behavior?
We no longer clean the
DataContext
, so subsequent clones are still working. This should not have any impact for 2-way binding as anyway theContent
of the original instance is being replaced by a new instance.PR Checklist
Screenshots Compare Test Run
results.