Administrative overhead for PR 5339 (#5342)

* Update release-channels.md and put Stable, Preview, Exp in correct order

Table should have the rows sorted by channel in the order Stable, Preview, Experimental, as this is the logical order that is also used for the navigation in the docs.

* Update support.md and include 1.7 SDK in table with supported Windows versions

As 1.7 SDK was released, it should be included in the table with supported Windows client/server versions

* This PR lists out an option for enterprise admins to block the Microsoft Store Web Installer on domain managed devices.

* update back navigation (#5333)

* add navigation articles for UWP

* remove UWP content

* add back nav guidelines moved from nav history doc

* update for WinUI 3

* fix yaml header

* fix links

* Update release date in documentation

* Kbridge/main/1.7 stable/rich edit box  mathmode (#5338)

* snapshot

* added math mode detail

* Move cross device people API topic in TOC

* Kbridge/main/multilingula app toolkit deprecation (#5339)

* added deprecation notices

* email link

* feedback revs

---------

Co-authored-by: Thomas Claudius Huber <thomas@thomasclaudiushuber.com>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Raunak Oberoi <63877080+desigrit@users.noreply.github.com>
Co-authored-by: Jim Walker <jimwalk@microsoft.com>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com>
Co-authored-by: John Kennedy <jken@microsoft.com>
Co-authored-by: Alvin Ashcraft <aashcraft@microsoft.com>
Co-authored-by: Alvin Ashcraft <73072+alvinashcraft@users.noreply.github.com>

Author: 8 people

hub/apps/design/basics/navigate-between-two-pages.md

@@ -5,7 +5,7 @@ ms.assetid: B65D33BA-AAFE-434D-B6D5-1A0C49F59664
 label: Navigation design basics
 template: detail.hbs
 op-migration-status: ready
-ms.date: 09/24/2020
+ms.date: 04/03/2025
 ms.topic: article
 keywords: windows 10, uwp
 ms.localizationpriority: medium
@@ -256,6 +256,59 @@ Embedded navigation elements can appear in a page's content. Unlike other naviga
     :::column-end:::
 :::row-end:::
 
+## Guidelines for custom back navigation behavior
+
+If you choose to provide your own back stack navigation, the experience should be consistent with other apps. We recommend that you follow the following patterns for navigation actions:
+
+<div class="mx-responsive-img">
+<table>
+<thead>
+<tr class="header">
+<th align="left">Navigation action</th>
+<th align="left">Add to navigation history?</th>
+</tr>
+</thead>
+<tbody>
+<tr class="odd">
+<td><strong>Page to page, different peer groups</strong></td>
+<td><strong>Yes</strong>
+<p>In this illustration, the user navigates from level 1 of the app to level 2, crossing peer groups, so the navigation is added to the navigation history.</p>
+<p><img src="images/back-nav/nav-pagetopage-diffpeers-imageonly1.png" alt="Diagram of navigation across peer groups showing the user navigating from group one to group two and the back to group one." /></p>
+<p>In the next illustration, the user navigates between two peer groups at the same level, again crossing peer groups, so the navigation is added to the navigation history.</p>
+<p><img src="images/back-nav/nav-pagetopage-diffpeers-imageonly2.png" alt="Diagram of navigation across peer groups showing the user navigating from group one to group two then on to group three and back to group two." /></p></td>
+</tr>
+<tr class="even">
+<td><strong>Page to page, same peer group, no on-screen navigation element</strong>
+<p>The user navigates from one page to another with the same peer group. There is no on-screen navigation element (such as <a href="/windows/apps/design/controls/navigationview">NavigationView</a>) that provides direct navigation to both pages.</p></td>
+<td><strong>Yes</strong>
+<p>In the following illustration, the user navigates between two pages in the same peer group, and the navigation should be added to the navigation history.</p>
+<p><img src="images/back-nav/nav-pagetopage-samepeer-noosnavelement.png" alt="Navigation within a peer group" /></p></td>
+</tr>
+<tr class="odd">
+<td><strong>Page to page, same peer group, with an on-screen navigation element</strong>
+<p>The user navigates from one page to another in the same peer group. Both pages are shown in the same navigation element, such as <a href="/windows/apps/design/controls/navigationview">NavigationView</a>.</p></td>
+<td><strong>It depends</strong>
+<p>Yes, add to the navigation history, with two notable exceptions. If you expect users of your app to switch between pages in the peer group frequently, or if you wish to preserve the navigational hierarchy, then do not add to the navigation history. In this case, when the user presses back, go back to the last page before the user navigated to the current peer group. </p>
+<p><img src="images/back-nav/nav-pagetopage-samepeer-yesosnavelement.png" alt="Navigation across peer groups when a navigation element is present" /></p></td>
+</tr>
+<tr class="even">
+<td><strong>Show a transient UI</strong>
+<p>The app displays a pop-up or child window, such as a dialog, splash screen, or on-screen keyboard, or the app enters a special mode, such as multiple selection mode.</p></td>
+<td><strong>No</strong>
+<p>When the user presses the back button, dismiss the transient UI (hide the on-screen keyboard, cancel the dialog, etc) and return to the page that spawned the transient UI.</p>
+<p><img src="images/back-nav/back-transui.png" alt="Showing a transient UI" /></p></td>
+</tr>
+<tr class="odd">
+<td><strong>Enumerate items</strong>
+<p>The app displays content for an on-screen item, such as the details for the selected item in list/details list.</p></td>
+<td><strong>No</strong>
+<p>Enumerating items is similar to navigating within a peer group. When the user presses back, navigate to the page that preceded the current page that has the item enumeration.</p>
+<p><img src="images/back-nav/nav-enumerate.png" alt="Iterm enumeration" /></p></td>
+</tr>
+</tbody>
+</table>
+</div>
+
 ## Next: Add navigation code to your app
 
 The next article, [Implement basic navigation](navigate-between-two-pages.md), shows the code required to use a `Frame` control to enable basic navigation between two pages in your app.