NavigationView on WinUI 3 is not aware of Window.ExtendsContentIntoTitleBar value and does not apply necessarily padding

Describe the bug

NavigationView on WinUI 3 (Windows App SDK 1.0 Preview 2) is currently not aware of the Window.ExtendsContentIntoTitleBar value. If we extends the content into the titlebar, no padding would be added on the NavigationView and this basically steals the input from the titlebar once being extended in. Also, if the Setting button is enabled, this also render the 3 captive buttons (minimize, maximize/windowing, close) from being clicked.

Steps to reproduce the bug

1. Create new WinUI 3 + .NET 5 project
2. On MainWindow, add a NavigationView control as the root content and set the PaneDispayMode to Top.
3. In MainWindow.xaml.cs, on the constructor, set ExtendsContentIntoTitleBar to true.
4. Build and run.

Expected behavior

The NavigationView control should have displayed their padding, but instead the control display no padding.

Screenshots

NuGet package version

No response

Windows app type

• UWP
• Win32

Device form factor

Desktop

Windows version

Insider Build (xxxxx)

Additional context

Observe on latest RTM Windows 11. 21H2 22000.194.

[gabbybilka]

@pratikone @karenbtlai What is the latest status on this issue?

[pratikone]

there isn’t a dedicated inset value so one can use 42 px x 3 padding on the right edge for leaving space for titlebar. edit : on a second thought, the custom titlebar is a lower level api which draws custom min max close buttons in xaml and present it on the window. the controls should not be made aware of titlebar dimensions as it would change (dragging region, no caption button regions). Handling all that logic will unnecessarily increase complexity of navigation view and other controls.

As a result, I think NavigationView should not be handling this special case automatically. App developer can use padding as suggested earlier. so navigationView should not be aware of titlebar and caption buttons dimensions automatically.
I am working on an easy way for one to get the right inset automatically (which will not include the draggable region). Do reach out if you are facing issues in doing the padding and re-open the bug. I am closing it for now.