From 33e3c53c9445e432131b148e8cd32bcdb33f9bf9 Mon Sep 17 00:00:00 2001 From: Martin Zikmund Date: Mon, 14 Oct 2024 15:36:48 +0200 Subject: [PATCH] docs: Additional docs for WinUI Frame behavior --- doc/articles/controls/Frame.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/articles/controls/Frame.md b/doc/articles/controls/Frame.md index af26406d396a..022b501dc0a6 100644 --- a/doc/articles/controls/Frame.md +++ b/doc/articles/controls/Frame.md @@ -12,3 +12,15 @@ uid: Uno.Controls.Frame ## Using Frame with Uno To improve performance during navigation, `Frame` on Android, iOS, and WebAssembly targets operates in different way than in WinUI. Whereas WinUI follows `NavigationCacheMode` property on individual `Page` instances, on iOS and Android we keep the individual page instances in the back stack in memory by default. This way the can be quickly surfaced back to the user during back navigation. This behavior can be controlled using the `FeatureConfiguration.Frame.UseWinUIBehavior` property. This defaults to `true` on Skia targets and to `false` on Android, iOS and WebAssembly. + +If you set `UseWinUIBehavior` to `true` on Android and iOS, you also need to override the default style for the control. You can do this by explicitly setting the `Style` to `XamlDefaultFrame`: + +```xml + +``` + +Or by creating an implicit style based on `XamlDefaultFrame`: + +```xml +