Merge pull request #3480 from MicrosoftDocs/main

main to live - 6/18/25

Author: captainbrosset

.openpublishing.redirection.json

@@ -154,6 +154,11 @@
         "redirect_url": "/microsoft-edge/devtools-guide-chromium/sensors/#simulate-device-orientation",
         "redirect_document_id": false
       },
+      {
+        "source_path": "./microsoft-edge/devtools-protocol-chromium/index.md",
+        "redirect_url": "/microsoft-edge/devtools/protocol/index",
+        "redirect_document_id": false
+      },
 // /Microsoft Edge DevTools
 // ============================================================================
 // Microsoft Edge extensions
@@ -1345,6 +1350,26 @@
         "redirect_url": "https://github.com/microsoft/edge-selenium-tools/wiki/using-gpg-to-verify-selenium-tools-for-microsoft-edge-releases",
         "redirect_document_id": false
       },
+      {
+        "source_path": "./microsoft-edge/webdriver-chromium/capabilities-edge-options.md",
+        "redirect_url": "/microsoft-edge/webdriver/capabilities-edge-options",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "./microsoft-edge/webdriver-chromium/contact.md",
+        "redirect_url": "/microsoft-edge/webdriver/contact",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "./microsoft-edge/webdriver-chromium/ie-mode.md",
+        "redirect_url": "/microsoft-edge/webdriver/ie-mode",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "./microsoft-edge/webdriver-chromium/index.md",
+        "redirect_url": "/microsoft-edge/webdriver/index",
+        "redirect_document_id": false
+      },
 // /WebDriver: "microsoft / edge-selenium-tools" repo
 // ============================================================================
 // Archived EdgeHTML content
@@ -4216,11 +4241,12 @@
         "redirect_url": "/archive/microsoft-edge/legacy/developer",
         "redirect_document_id": false
       },
+      /* reused this source_path for Edge Chromium article
       {
         "source_path": "./microsoft-edge/webdriver/index.md",
         "redirect_url": "/archive/microsoft-edge/legacy/developer",
         "redirect_document_id": false
-      },
+      },*/
       {
         "source_path": "./microsoft-edge/webdriver/dialogs.md",
         "redirect_url": "/archive/microsoft-edge/legacy/developer",

microsoft-edge/developer/index.yml

@@ -210,7 +210,7 @@ landingContent:
             url: ../test-and-automation/test-and-automation.md
 
           - text: DevTools Protocol
-            url: ../devtools-protocol-chromium/index.md   # https://learn.microsoft.com/microsoft-edge/devtools-protocol-chromium/
+            url: ../test-and-automation/devtools-protocol.md  # jump page
 
           - text: Use Playwright to automate and test in Microsoft Edge
             url: ../playwright/index.md
@@ -219,7 +219,7 @@ landingContent:
             url: ../puppeteer/index.md
 
           - text: Use WebDriver to automate Microsoft Edge
-            url: ../webdriver-chromium/index.md
+            url: ../webdriver/index.md
 
           - text: webhint extension for Visual Studio Code
             url: ../visual-studio-code/webhint.md

microsoft-edge/devtools-guide-chromium/ie-mode/index.md

@@ -75,7 +75,7 @@ Microsoft Edge doesn't support automating IE mode through the `InternetExplorer`
 
 If your automation application doesn't require IE mode for the website (or app) content to function correctly, we recommend updating your application to use Microsoft Edge instead of Internet Explorer 11. Many available automation tools support Microsoft Edge, including WebDriver and Playwright.
 
-*  To learn more about automating Microsoft Edge using WebDriver, see [Use WebDriver to automate Microsoft Edge](../../webdriver-chromium/index.md).
+*  To learn more about automating Microsoft Edge using WebDriver, see [Use WebDriver to automate Microsoft Edge](../../webdriver/index.md).
 *  To learn more about using Playwright, see [Use Playwright to automate and test in Microsoft Edge](../../playwright/index.md).
 
 Applications that require IE mode for the website (or app) content to function correctly should use the `WebBrowser` control.  The `WebBrowser` control uses the Internet Explorer platform (MSHTML/Trident) to render web content, and will work even if the Internet Explorer 11 desktop application isn't available.

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

@@ -34,12 +34,12 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 Microsoft Edge Dev is now supported on Ubuntu, Debian, Fedora, and openSUSE distributions.  Download and install the Microsoft Edge Dev `.deb` or `.rpm` package directly from the [Microsoft Edge Insider site](https://www.microsoft.com/edge/download/insider?platform=linux) or use the standard package management tools of your Linux distribution.
 
-If you are using a Linux environment in your continuous integration and delivery (CI/CD) solutions, Microsoft Edge WebDriver is also available on Linux.  To get started automating Microsoft Edge with Microsoft Edge WebDriver, see [Recent versions](https://developer.microsoft.com/microsoft-edge/tools/webdriver#downloads) at the Microsoft Edge WebDriver page.  For help with automating Microsoft Edge with Microsoft Edge WebDriver, see [Use WebDriver for test automation](../../../../webdriver-chromium/index.md).
+If you are using a Linux environment in your continuous integration and delivery (CI/CD) solutions, Microsoft Edge WebDriver is also available on Linux.  To get started automating Microsoft Edge with Microsoft Edge WebDriver, see [Recent versions](https://developer.microsoft.com/microsoft-edge/tools/webdriver#downloads) at the Microsoft Edge WebDriver page.  For help with automating Microsoft Edge with Microsoft Edge WebDriver, see [Use WebDriver for test automation](../../../../webdriver/index.md).
 
 ![DevTools in Microsoft Edge on Linux](./devtools-images/edge-on-linux.png)
 
 See also:
-* [Use WebDriver to automate Microsoft Edge](../../../../webdriver-chromium/index.md)
+* [Use WebDriver to automate Microsoft Edge](../../../../webdriver/index.md)
 
 
 <!-- ====================================================================== -->

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

@@ -46,7 +46,7 @@ Update: Starting with Microsoft Edge 131, the Visual Studio Code themes feature
 Starting June 15, 2022, Internet Explorer 11 will no longer be supported on certain versions of Windows 10.  IE mode is a feature of Microsoft Edge for organizations that still need Internet Explorer 11 for compatibility with legacy websites or apps.  To support testing of those legacy websites and apps, you can now automate IE mode with Selenium 4 and Internet Explorer Driver.
 
 See also:
-* [Use Internet Explorer Driver to automate IE mode in Microsoft Edge](../../../../webdriver-chromium/ie-mode.md)
+* [Use Internet Explorer Driver to automate IE mode in Microsoft Edge](../../../../webdriver/ie-mode.md)
 
 
 <!-- ====================================================================== -->

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

@@ -39,7 +39,7 @@ To download Microsoft Edge WebDriver on Apple M1 devices:
 Thank you for your feedback on this issue!
 
 See also:
-* [Use WebDriver to automate Microsoft Edge](../../../../webdriver-chromium/index.md)
+* [Use WebDriver to automate Microsoft Edge](../../../../webdriver/index.md)
 * [Microsoft Edge WebDriver](https://developer.microsoft.com/microsoft-edge/tools/webdriver/)
 * [Issue #17: Support for Apple silicon](https://github.com/MicrosoftEdge/EdgeWebDriver/issues/17)
 

…edge/devtools-protocol-chromium/index.md microsoft-edge/devtools/protocol/index.mdmicrosoft-edge/devtools-protocol-chromium/index.md renamed to microsoft-edge/devtools/protocol/index.md microsoft-edge/devtools-protocol-chromium/index.md renamed to microsoft-edge/devtools/protocol/index.md

@@ -9,12 +9,7 @@ ms.date: 04/06/2021
 ---
 # Microsoft Edge DevTools Protocol
 
-Use the DevTools Protocol to instrument, inspect, debug, and profile browsers including Microsoft Edge.  The Microsoft Edge DevTools Protocol matches the APIs of the Chrome DevTools Protocol.  For reference documentation, go to [Chrome DevTools Protocol Viewer](https://chromedevtools.github.io/devtools-protocol/tot).
-
-> [!NOTE]
-> With the shift in the underlying web platform of Microsoft Edge to Chromium, the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) won't be receiving any further updates.  Going forward, the Microsoft Edge DevTools Protocol will match the APIs of the Chrome DevTools Protocol.
->
-> Any methods that were prefixed with `ms` in the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) are no longer supported in the Microsoft Edge DevTools Protocol.
+Use the DevTools Protocol to instrument, inspect, debug, and profile browsers including Microsoft Edge.  The Microsoft Edge DevTools Protocol matches the APIs of the Chrome DevTools Protocol.  For Reference documentation, see [Chrome DevTools Protocol Viewer](https://chromedevtools.github.io/devtools-protocol/tot).
 
 
 <!-- ====================================================================== -->
@@ -133,11 +128,11 @@ String("Target is closing")
 
 You can install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).  This app enables you to remotely debug Microsoft Edge running on a Windows 10 or later device from your development machine.
 
-To learn how to set up your Windows device and connect to it from your development machine, see [Get started with remote debugging Windows devices](../devtools-guide-chromium/remote-debugging/windows.md).
+To learn how to set up your Windows device and connect to it from your development machine, see [Remotely debug Windows devices](../../devtools-guide-chromium/remote-debugging/windows.md).
 
-The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) uses the same Microsoft Edge DevTools Protocol as [DevTools](../devtools-guide-chromium/overview.md) to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.  It supports the following HTTP endpoints.
+The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) app uses the same Microsoft Edge DevTools Protocol as used by Microsoft Edge DevTools, to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.
 
-The following Reference sections are for Remote Tools for Microsoft Edge.
+The Remote Tools for Microsoft Edge app supports the following HTTP endpoints; the Reference sections below are for Remote Tools for Microsoft Edge.
 
 
 <!-- ====================================================================== -->
@@ -161,7 +156,7 @@ None.
 <!-- ====================================================================== -->
 ## /msedge/json/list
 
-Provides a candidate list of all Microsoft Edge and WebView2 Runtime processes running on the connected device (including [PWAs](../progressive-web-apps-chromium/index.md)) and all tabs or targets in each process available for debugging.
+Provides a candidate list of all Microsoft Edge and WebView2 Runtime processes running on the connected device (including PWAs) and all tabs or targets in each process available for debugging.
 
 **Parameters**
 
@@ -201,6 +196,9 @@ None.
 ]
 ```
 
+See also:
+* [Overview of Progressive Web Apps (PWAs)](../../progressive-web-apps-chromium/index.md)
+
 
 <!-- ====================================================================== -->
 ## /msedge/
@@ -273,9 +271,17 @@ None.
 JSON object which represents the available API surface for the version of the protocol that the Microsoft Edge instance that matches the provided `[pid]` is using.
 
 
+<!-- ====================================================================== -->
+## EdgeHTML DevTools Protocol
+
+With the shift in the underlying web platform of Microsoft Edge to Chromium, the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) won't be receiving any further updates.  Going forward, the Microsoft Edge DevTools Protocol will match the APIs of the Chrome DevTools Protocol.
+
+Any methods that were prefixed with `ms` in the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) are no longer supported in the Microsoft Edge DevTools Protocol.
+
+
 <!-- ====================================================================== -->
 ## See also
 
 * [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/)
-* [Chrome DevTools Protocol (CDP)](../webview2/concepts/overview-features-apis.md#chrome-devtools-protocol-cdp) in _Overview of WebView2 APIs_
-* [Use the Chrome DevTools Protocol (CDP) in WebView2 apps](../webview2/how-to/chromium-devtools-protocol.md)
+* [Chrome DevTools Protocol (CDP)](../../webview2/concepts/overview-features-apis.md#chrome-devtools-protocol-cdp) in _Overview of WebView2 APIs_.
+* [Use the Chrome DevTools Protocol (CDP) in WebView2 apps](../../webview2/how-to/chromium-devtools-protocol.md)

microsoft-edge/extensions-chromium/update/api/addons-api-reference.md

@@ -189,7 +189,7 @@ There are several responses, for different scenarios.
 ###### Response when the operation fails with errors
 
 ```json
- {
+{
     "id": "{operationID}",
     "createdTime": "Date Time",
     "lastUpdatedTime": "Date Time",

microsoft-edge/extensions-chromium/update/api/using-addons-api.md

@@ -546,6 +546,129 @@ See also:
 * [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_.
 
 
+<!-- ====================================================================== -->
+## Example: Check publication status and publish an extension with a PowerShell script
+
+The following code is an example of a PowerShell script that uses the REST API to check the publication status of an extension, and publish that extension.
+
+To use this script, fill in the `$ClientID`, `$ClientSecret`, `$ProductID`, and `$FilePATH` values at the top of the script.
+
+```powershell
+Param(
+    [string] $ClientID = '',
+    [string] $ClientSecret = '',
+    [string] $ProductID = '',
+    [string] $FilePATH = '',
+    [int] $RetryLimit = 10,
+    [int] $RetryAfterPeriod = 5,
+    [string] $ApiEndpoint = 'https://api.addons.microsoftedge.microsoft.com',
+    [string] $PublishNotes = 'This is a test publish'
+)
+
+function ReadKeyFromJSON($jsonContent, $keyToFetch){
+    $jsonContent.TrimStart('{').TrimEnd('}').Split(',') |ForEach-Object {
+        $key,$value = $_.Split(':')
+        if($key.Trim('"') -eq $keyToFetch) {
+            return $value.Trim('"')
+        }
+    }
+    return ''
+}
+
+function ReadLocationFromRawContent($jsonRawContent) {
+    $jsonRawContent.Split([System.Environment]::NewLine, [System.StringSplitOptions]::RemoveEmptyEntries) | ForEach-Object {
+        $key,$value = $_.Split(':')
+        if ($key -eq 'Location') {
+            return $value
+        }
+    }
+    return ''
+}
+
+$PublishNotesBody = @{
+    notes = $PublishNotes
+}
+
+$GetTokenHeaders = @{
+    'Content-Type' = 'application/x-www-form-urlencoded'
+}
+
+$UploadHeaders = @{
+    "Authorization" = "ApiKey $ClientSecret"
+    "Content-Type" = "application/zip"
+    "X-ClientID" = "$ClientID"
+}
+
+$uploadResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$ProductID/submissions/draft/package" -Headers $UploadHeaders -Method 'POST' -InFile $FilePATH
+
+$uploadResponse
+
+$uploadOperationId = ''
+
+if($uploadResponse.StatusCode -eq 202) {
+    "Upload Successful"
+    $uploadOperationId = ReadLocationFromRawContent($uploadResponse.RawContent)
+}
+
+$uploadStatusResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$ProductID/submissions/draft/package/operations/$UploadOperationId" -Headers $UploadHeaders -Method 'GET'
+
+$uploadStatusResponse
+
+$uploadStatus = 'InProgress'
+
+if($uploadStatusResponse.StatusCode -eq 202) {
+    "Upload Status Received Successfully"
+    $retryCount = 1;
+    while($uploadStatus -eq 'InProgress') {
+        if($retryCount -gt $RetryLimit) {
+            Exit-PSSession
+        }
+        $uploadStatusResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$ProductID/submissions/draft/package/operations/$UploadOperationId" -Headers $UploadHeaders -Method 'GET'
+        $retryCount = $retryCount + 1
+        Start-Sleep -Seconds $RetryAfterPeriod
+        $uploadStatus = ReadKeyFromJSON($uploadStatusResponse.Content, 'status')
+    }
+}
+
+$publishResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$productID/submissions" -Headers $UploadHeaders -Method 'POST' -Body $PublishNotesBody
+
+$publishResponse
+
+$PublishOperationId = ''
+
+if($publishResponse.StatusCode -eq 202) {
+    "Published Successfully"
+    $PublishOperationId = ReadLocationFromRawContent($publishResponse.RawContent)
+}
+
+$PublishOperationId
+
+$publishStatusResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$ProductID/submissions/operations/$PublishOperationId" -Headers $UploadHeaders -Method 'GET'
+
+$publishStatusResponse
+
+$publishStatus = 'InProgress'
+
+$publishStatusResponse.Content
+
+if($publishStatusResponse.StatusCode -eq 202) {
+    "Publish Status Received Successfully"
+    $retryCount = 1;
+    while($publishStatus -eq 'InProgress') {
+        if($retryCount -gt $RetryLimit) {
+            Exit-PSSession
+        }
+        $publishStatusResponse = Invoke-WebRequest "$ApiEndpoint/v1/products/$ProductID/submissions/operations/$PublishOperationId" -Headers $UploadHeaders -Method 'GET'
+        $retryCount = $retryCount + 1
+        Start-Sleep -Seconds $RetryAfterPeriod
+        $publishStatus = ReadKeyFromJSON($publishStatusResponse.Content, 'status')
+    }
+}
+
+$publishStatus
+```
+
+
 <!-- ====================================================================== -->
 ## See also
 <!-- all links in article -->

microsoft-edge/index.yml

@@ -368,7 +368,7 @@ conceptualContent:
               itemType: overview
 
             - text: DevTools Protocol
-              url: ./test-and-automation/devtools-protocol.md
+              url: ./test-and-automation/devtools-protocol.md  # jump page
               itemType: how-to-guide
 
             - text: Use Playwright to automate and test in Microsoft Edge
@@ -380,7 +380,7 @@ conceptualContent:
               itemType: how-to-guide
 
             - text: Use WebDriver to automate Microsoft Edge
-              url: ./webdriver-chromium/index.md
+              url: ./webdriver/index.md
               itemType: how-to-guide
 
             - text: webhint extension for Visual Studio Code