Merge branch 'main' into user/mikehoffms/relnotes-release-119

microsoft-edge/devtools-guide-chromium/about-tools.md

@@ -137,4 +137,4 @@ To restore all of the default tabs on the main toolbar:
 ## See also
 
 * [Overview of DevTools](overview.md) - Similar to the present article, but broader coverage, with a top-level introduction of DevTools.
-* [Simplify DevTools using Focus Mode](experimental-features/focus-mode.md), in _Experimental features_.  In **Focus Mode**, the **Activity Bar** is a compact replacement for the main toolbar, and the **Quick View** list is a replacement for the tabs on the Drawer toolbar.
+* [Simplify DevTools using Focus Mode](experimental-features/focus-mode.md) - In **Focus Mode**, the **Activity Bar** is a compact replacement for the main toolbar, and the **Quick View** list is a replacement for the tabs on the Drawer toolbar.

microsoft-edge/devtools-guide-chromium/experimental-features/index.md

@@ -1,5 +1,5 @@
 ---
-title: Experimental features
+title: Experimental features in Microsoft Edge DevTools
 description: The latest experimental features in Microsoft Edge DevTools.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,7 +8,7 @@ ms.prod: microsoft-edge
 no-loc: ["Enable webhint"]
 ms.date: 10/23/2023
 ---
-# Experimental features
+# Experimental features in Microsoft Edge DevTools
 
 <!-- 
 Policies to keep this page comprehensive and maintainable: 

microsoft-edge/devtools-guide-chromium/landing/index.yml

@@ -73,7 +73,7 @@ landingContent:
             url: /microsoft-edge/devtools-guide-chromium/customize/theme
       - linkListType: whats-new
         links:
-          - text: Experimental features
+          - text: Experimental features in Microsoft Edge DevTools
             url: /microsoft-edge/devtools-guide-chromium/experimental-features/index
       - linkListType: how-to-guide
         links:

microsoft-edge/devtools-guide-chromium/network-console/network-console-tool.md

@@ -61,8 +61,7 @@ To use the **Network Console** starting from the **Network** tool:
 
    ![Editing the network request and then clicking Send, in the Network Console tool](./network-console-tool-images/edit-then-send.png)
 
-   <!-- Another screenshot (used by Experimental Features article)
-
+   <!-- another screenshot (used by "Experimental features in Microsoft Edge DevTools" article):
    ![The Network Console tool in the main toolbar](../media/network-network-console.png) -->
 
 

microsoft-edge/devtools-guide-chromium/overview.md

@@ -551,7 +551,7 @@ You can also change the settings of advanced features, such as:
 <!-- ====================================================================== -->
 ## Trying experimental features
 
-The DevTools team provides new features as _experiments_ in DevTools.  You can turn each of the experiments on or off.  To see the full list of [Experimental features](experimental-features/index.md), in DevTools, select **Settings** (the gear icon), and then select **Experiments**.
+The DevTools team provides new features as _experiments_ in DevTools.  You can turn each of the experiments on or off.  To see the full list of [Experimental features in Microsoft Edge DevTools](experimental-features/index.md), in DevTools, select **Settings** (![Settings icon](./overview-images/settings-gear-icon-light-theme.png)), and then select **Experiments**.
 
 To preview the [latest features coming to DevTools](whats-new/2021/02/devtools.md), download [Microsoft Edge Canary](https://www.microsoft.com/edge/download/insider), which builds nightly.
 

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md

@@ -99,7 +99,7 @@ Chromium issue [#1070378](https://crbug.com/1070378)
 
 See also:
 * [webhint extension for Visual Studio Code](../../../../test-and-automation/webhint.md)
-* [Enable webhint](../../../experimental-features/index.md#enable-webhint) in _Experimental features_
+* [Enable webhint](../../../experimental-features/index.md#enable-webhint) in _Experimental features in Microsoft Edge DevTools_
 
 
 <!-- ====================================================================== -->
@@ -324,7 +324,7 @@ Update: As of 2022, breakpoints are now indicated by a blue rectangle, instead o
 The **Sources** panel has new designs for breakpoints, conditional breakpoints, and logpoints.  Breakpoints are represented by a red circle, just like [Visual Studio Code](https://code.visualstudio.com/) and [Visual Studio](https://visualstudio.microsoft.com/).  Icons are added to differentiate conditional breakpoints and logpoints.
 
 <!-- todo: update capture -->
-![Breakpoints](./devtools-images/breakpoints.png)
+![Breakpoint indicators](./devtools-images/breakpoints.png)
 
 Chromium issue [#1041830](https://crbug.com/1041830)
 

microsoft-edge/devtools-guide-chromium/whats-new/2021/01/devtools.md

@@ -68,7 +68,7 @@ To turn on this experiment, see [Settings](../../../customize/index.md#settings)
 For the history of this feature in the Chromium open-source project, see Issue [1093229](https://crbug.com/1093229).
 
 See also:
-* [Enable the Font Editor tool within the Styles pane](../../../experimental-features/index.md#enable-the-font-editor-tool-within-the-styles-pane) in _Experimental features_.
+* [Enable the Font Editor tool within the Styles pane](../../../experimental-features/index.md#enable-the-font-editor-tool-within-the-styles-pane) in _Experimental features in Microsoft Edge DevTools_.
 * [Edit CSS font styles and settings in the Styles pane in DevTools](../../../inspect-styles/edit-fonts.md).
 
 
@@ -511,7 +511,7 @@ To turn on this experiment, select **Settings** > **Experiments** and then selec
 ![APCA in the Color Picker](./devtools-images/advanced-perceptual-contrast-algorithm.png)
 
 See also:
-* [Enable new Advanced Perceptual Contrast Algorithm (APCA) replacing previous contrast ratio and AA/AAA guidelines](../../../experimental-features/index.md#enable-new-advanced-perceptual-contrast-algorithm-apca-replacing-previous-contrast-ratio-and-aaaaa-guidelines) in _Experimental features_.
+* [Enable new Advanced Perceptual Contrast Algorithm (APCA) replacing previous contrast ratio and AA/AAA guidelines](../../../experimental-features/index.md#enable-new-advanced-perceptual-contrast-algorithm-apca-replacing-previous-contrast-ratio-and-aaaaa-guidelines) in _Experimental features in Microsoft Edge DevTools_.
 Edge 89)_.
 * [Change colors with the Color Picker](../../../css/reference.md#change-colors-with-the-color-picker) in _CSS features reference_.
 * [Test text-color contrast using the Color Picker](../../../accessibility/color-picker.md)

microsoft-edge/devtools-guide-chromium/whats-new/2021/02/devtools.md

@@ -71,7 +71,7 @@ Note: As of May 2022, tooltips aren't supported from the **Activity Bar**; that
 <!-- ![Click the Help (?) icon in the Activity Bar to display tooltips](../../media/2021/02/focus-mode-and-tooltips-help.png) -->
 <!--
 See also:
-* [Focus Mode](../../../experimental-features/index.md#focus-mode) in _Experimental features_.
+* [Focus Mode](../../../experimental-features/index.md#focus-mode) in _Experimental features in Microsoft Edge DevTools_.
 -->
 
 See also:
@@ -82,7 +82,6 @@ See also:
 ## Customize keyboard shortcuts in Settings
 
 <!-- Title: Change keyboard shortcuts in Settings  -->
-<!-- TODO:  Rachel's feedback is about the fact that this experimental feature is turned on by default, may have separate section in What's New for experimental features)  -->
 <!-- Subtitle: Make DevTools work better for you by creating new keyboard shortcuts for any action in the DevTools.  -->
 
 You can now customize the keyboard shortcut for any action in the DevTools.

microsoft-edge/devtools-guide-chromium/whats-new/2021/04/devtools.md

@@ -383,7 +383,7 @@ Find experiments quicker with the new experiment filter.  For example, to turn o
 ![Filter experiments in the Experiments setting](./devtools-images/settings-experiments-filter-by-issues.png)
 
 See also:
-* [Experimental features](../../../experimental-features/index.md)
+* [Experimental features in Microsoft Edge DevTools](../../../experimental-features/index.md)
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools-guide-chromium/whats-new/2022/01/devtools.md

@@ -74,7 +74,7 @@ Thanks to your early feedback, we've continued to make improvements and bug fixe
 When using Focus Mode, all the same tools and custom themes are available as in the existing DevTools UI.  Try Focus Mode for yourself by enabling the **Focus Mode** experiment in DevTools **Settings** > **Experiments**.
 
 See also:
-* [Focus Mode](../../../experimental-features/index.md#focus-mode) in _Experimental features_
+* [Focus Mode](../../../experimental-features/index.md#focus-mode) in _Experimental features in Microsoft Edge DevTools_.
 * [Simplify DevTools using Focus Mode](../../../experimental-features/focus-mode.md)
 * [Apply a color theme to DevTools](../../../customize/theme.md)
 

microsoft-edge/devtools-guide-chromium/whats-new/2022/05/devtools-102.md

@@ -147,7 +147,7 @@ In the **Settings** > **Experiments** page, each experiment now has a **Help** (
 
 ![Help icons for Settings > Experiments checkboxes](devtools-102-images/settings-experiments-help-icons.png)
 
-To get more information about an experimental feature, click the corresponding **Help** (![Help icon](devtools-102-images/settings-experiments-help-icon.png)) button.  The **Help** button displays the relevant section of the [Experimental features](../../../experimental-features/index.md) article.
+To get more information about an experimental feature, click the corresponding **Help** (![Help icon](devtools-102-images/settings-experiments-help-icon.png)) button.  The **Help** button displays the relevant section of the [Experimental features in Microsoft Edge DevTools](../../../experimental-features/index.md) article.
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools-guide-chromium/whats-new/2023/03/devtools-111.md

@@ -28,7 +28,7 @@ To give us feedback on the remote debugging flow for Microsoft Edge, leave a com
 See also:
 * [Remotely debug Windows devices](../../../remote-debugging/windows.md)
 * [Windows Device Portal for Desktop](/windows/uwp/debug-test-perf/device-portal-desktop)
-* [Remote debugging WebView2 WinUI 2 (UWP) apps with Remote Tools for Microsoft Edge](../../../../webview2/how-to/remote-debugging.md)
+* [Remote debugging WebView2 WinUI 2 (UWP) apps](../../../../webview2/how-to/remote-debugging.md)
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md

@@ -11,6 +11,8 @@ ms.date: 08/18/2023
 
 [!INCLUDE [Microsoft Edge team note for top of What's New](includes/edge-whats-new-note.md)]
 
+What's New articles correspond to historical releases of Microsoft Edge, and are not updated over time.  References to "new features" and "experiments" might become outdated as new versions of Microsoft Edge are released.
+
 <!-- maintenance notes:
 * add the new page to toc.yml
 * move eleventh oldest link into whats-new-archive.md

microsoft-edge/origin-trials/index.md

@@ -5,99 +5,22 @@ author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
 ms.prod: microsoft-edge
-ms.date: 02/02/2023
+ms.date: 10/25/2023
 ---
 # Use Origin Trials in Microsoft Edge
 
+You can use Origin Trials to try out experimental APIs on your own live site for a limited period of time.  When using Origin Trials, users of Microsoft Edge that visit your site might run code that uses experimental APIs.
 
-You can use Origin Trials to try out experimental APIs on live sites for a limited period of time.  When using Origin Trials, users of Microsoft Edge that visit your site may run code that uses experimental APIs.  To access the experimental APIs on each user machine, you don't need to go to `edge://flags` and turn on feature flags.
+To support the experimental APIs, users don't need to go to `edge://flags` on their own device to access the experimental APIs that your site uses.  Instead, you register the origin that you want to use the experimental feature on (for example, `https://www.contoso.com:443`), and you'll then be sent a token that you add to the code of your website.
 
-Instead, you register the origin (for example, `https://www.contoso.com:443`) that you want to use the experimental feature on and you'll be issued a token that you add to the code of your website.
+To see a list of the available origin trials and register your origin to give them a try, see [Microsoft Edge Origin Trials](https://microsoftedge.github.io/MSEdgeExplainers/origin-trials/).  To assess the suitability of using the experimental APIs on your website, check the minimum version requirements for Microsoft Edge, and the trial end date.
 
-To see a list of the available origin trials and register your origin to give them a try, see the [Microsoft Edge Origin Trials Developer Console](https://developer.microsoft.com/microsoft-edge/origin-trials/).  You can also provide feedback to browser engineers and the web standards community about the design of the API, your use cases, or your experience using the APIs.
+You can also provide feedback to browser engineers and the web standards community about the design of the API, your use cases, or your experience using the APIs.
 
+For more information, see the **Getting Started** and **Developer Guidelines** sections in [Microsoft Edge Origin Trials](https://microsoftedge.github.io/MSEdgeExplainers/origin-trials/).
 
-<!-- ====================================================================== -->
-## Get started using Origin Trials
-
-For more information about the experimental APIs available in Microsoft Edge, see [Microsoft Edge Origin Trials Developer Console](https://developer.microsoft.com/microsoft-edge/origin-trials).  Be sure to review the minimum version requirements for Microsoft Edge, and the trial end date, to assess the suitability of using the experimental APIs on your website.
-
-> [!NOTE]
-> An experiment may end earlier than planned if any of the following situations occur:
-> *   A major security incident.
-> *   If sufficient feedback is collected that indicates a major redesign is needed to meet the needs of web developers.
-> In either case, a notification email is sent to all developers currently enrolled in the experiment.
-
-### Register for a trial of an experimental API
-
-To register for a trial of an experimental API:
-
-1. Go to [Microsoft Edge Origin Trials Developer Console](https://developer.microsoft.com/microsoft-edge/origin-trials).
-
-1. Click the **Register** button on any of the available experiments.
-
-1. Sign in to the Developer Console using your GitHub username and password.
-
-1. Click **Authorize MicrosoftEdge**.
-
-1. Complete the form.
-
-   > [!NOTE]
-   > To enroll a single or all subdomains, choose set the `Do you need to match all subdomains for the provided origin?` setting to `Yes`.  For example, `https://dev.contoso.com` is a single domain, and `https://*.contoso.com` uses a wildcard to represent all subdomains.
-
-   > [!IMPORTANT]
-   > The following origin formats aren't allowed.
-   > *   Specifying a subfolder on the origin.  For example, `https://contoso.com/path/subfolder`
-   >
-   > *   Using an origin with query string parameters.  For example, `https://contoso.com/path/feature?query_parameter=12345`
-
-1. Click **ACCEPT and REGISTER**.
-
-### Apply your token
-
-A token is instantly generated and displayed on the [Microsoft Edge Origin Trials Developer Console](https://developer.microsoft.com/microsoft-edge/origin-trials).  To begin using the trial on your website, use either of the following methods to apply the token to your page:
-
-*  Add the `origin-trial` attribute value and your token to the `meta` tag on every page that uses the experimental API.
 
-   ```html
-   <meta http-equiv="origin-trial" content="replace-with-your-token">
-   ```
-
-*  Add `Origin-Trial` to the HTTP response header of your server.
-
-   ```json
-   Origin-Trial: replace-with-your-token
-   ```
-
-> [!NOTE]
-> Your token is valid for 6 weeks.  Before your trial ends, reminder emails are sent to you that ask for your feedback and ask you to consider renewing your trial before your token expires.
-
-### Opt out of an experiment
-
-To opt out of an experiment, use one of the following methods to remove your token.
-
-*  Remove the `meta` tag from every page that used the experimental API.
-
-   ```html
-   <meta http-equiv="origin-trial" content="your-token">
-   ```
-
-*  Remove `Origin-Trial` from the HTTP response header of your server.
-
-   ```json
-   Origin-Trial: your-token
-   ```
-
-### Detect experimental features and provide a fallback
-
-When using experimental APIs, ensure you provide a working experience to all visitors of your website.  Visitors may use browsers that don't support the experimental APIs that you added to your code.  Additionally, if your token expires before you renew it, the experimental API is no longer available, which may result in errors.
-
-To avoid this situation, make sure you detect features available in your browser.  For more information, see [Implementing feature detection](https://developer.mozilla.org/docs/learn/tools_and_testing/cross_browser_testing/feature_detection).
-
-### Roadmap for Allowed Origins
-
-The Microsoft Edge Origin Trials portal today only supports SSL Enabled Origins, which means that websites must have HTTPS properly implemented to register for an experiment.  In the future, the following secure origins are planned:
-
-*  Register `http://localhost` as the origin for your experiments.  To use `http://localhost` today, go to `edge://flags` and set the experiment to **Enabled**.
+<!-- ====================================================================== -->
+## See also
 
-*  Use extensions with `extensions://` prefixed origins to enroll in experiments.
+* [Experimental features and origin trials](../progressive-web-apps-chromium/how-to/origin-trials.md) in the Progressive Web Apps (PWA) docs

microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls.md

@@ -10,10 +10,17 @@ ms.date: 09/15/2022
 ---
 # Handle links to your Progressive Web Apps
 
-Native applications on many operating systems can handle links. Native applications can request to be launched, instead of the web browser, when associated URLs are activated, to create a more engaging experience for these applications.
+Native apps on many operating systems can handle links.  When associated URLs are activated, native apps can request to be launched instead of the web browser, to create a more engaging experience for these apps.
 
 Progressive Web Apps (PWAs) can also handle links in a similar way.
 
+<!--
+link handling vs. url handling:
+Although the present filename is handle-urls.md, this file was repurposed to cover link handling rather than URL handlers.
+The PWA URL handlers feature was removed from Chromium.
+See also [PWAs as URL Handlers](https://web.dev/pwa-url-handler/).
+-->
+
 
 <!-- ====================================================================== -->
 ## Automatic link handling
@@ -49,4 +56,4 @@ Once the feature can be used in Microsoft Edge, we will document it here. In the
 <!-- ====================================================================== -->
 ## See also
 
-*  [PWAs as URL Handlers](https://web.dev/pwa-url-handler/).
+* [PWAs as URL Handlers](https://web.dev/pwa-url-handler/)