-
Notifications
You must be signed in to change notification settings - Fork 49
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
Expose created Maui view on the Maui Host #1803
Conversation
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-moss-0c5b8040f-1803.eastus2.azurestaticapps.net |
face182
to
d5af855
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-moss-0c5b8040f-1803.eastus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-moss-0c5b8040f-1803.eastus2.azurestaticapps.net |
@mergify backport legacy/2x |
✅ Backports have been created
|
@mergify backport release/stable/2.5 |
✅ Backports have been created
|
….5/pr-1803 Expose created Maui view on the Maui Host (backport #1803)
Expose created Maui view on the Maui Host (backport #1803)
GitHub Issue (If applicable): #
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The Maui content is silently created by the MauiHost and is not exposed
What is the new behavior?
The created VisualElement is now exposed through the Content property of the MauiHost. A new MauiContentCreated event has been added which can additionally be hooked onto to register a callback that should execute when the view is created.
cc: @dotMorten