uno-navigation-xaml

You can handle XAML navigation in Uno Platform without code-behind by using the uen:Navigation.Request attached property on interactive controls like Button or ListView to drive route-based transitions within a Frame shell.

Declarative navigation in Uno Platform works by attaching Navigation.Request to controls for route transitions and using Navigation.Data to pass bound data to target pages, eliminating manual navigation logic in code-behind.

Yes, you can pass data between pages during XAML navigation in Uno Platform by using the Navigation.Data attached property to bind and transfer state directly to target pages without code-behind.

Yes, Uno Platform XAML navigation supports interactive controls like ListView and ItemsRepeater. The Navigation.Request attached property applies to these controls to trigger route-based transitions from within a simple Frame shell.

The best way to manage the back-stack in Uno Platform XAML applications is using declarative Navigation.Request attached properties within a simple Frame shell, which handles route registration and back-stack management without code-behind.

Yes, you need a simple Frame shell and proper route registration in shell templates to use declarative navigation. The Navigation.Request and Navigation.Data attached properties rely on this shell structure to scaffold pages and routes.