Merge pull request #2896 from mikehoffms/user/mikehoffms/dmc-to-lmc

Changed docs.microsoft.com to learn.microsoft.com

Author: peiche-ms

specs/BrowserProcessExited.md

@@ -278,7 +278,7 @@ is that `BrowserProcessExited` is raised for any **browser process** exit
 `ProcessFailed` is raised for **unexpected** process exits of any kind (browser,
 render, GPU, and all other types), or for main frame **render process**
 unresponsiveness. To learn more about the WebView2 Process Model, go to
-[Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
+[Process model](https://learn.microsoft.com/microsoft-edge/webview2/concepts/process-model).
 
 In the case the browser process crashes, both `BrowserProcessExited` and
 `ProcessFailed` events are raised, but the order is not guaranteed.
@@ -318,7 +318,7 @@ interface ICoreWebView2Environment3 : ICoreWebView2Environment2
   /// due to browser process failure or normal shutdown (for example, when all
   /// associated WebViews are closed), after all resources have been released
   /// (including the user data folder). To learn about what these processes are,
-  /// go to [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
+  /// go to [Process model](https://learn.microsoft.com/microsoft-edge/webview2/concepts/process-model).
   ///
   /// A handler added with this method is called until removed with
   /// `remove_BrowserProcessExited`, even if a new browser process is bound to
@@ -344,7 +344,7 @@ interface ICoreWebView2Environment3 : ICoreWebView2Environment2
   /// **unexpected** process exits of any kind (browser, render, GPU, and all
   /// other types), or for main frame **render process** unresponsiveness. To
   /// learn more about the WebView2 Process Model, go to
-  /// [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
+  /// [Process model](https://learn.microsoft.com/microsoft-edge/webview2/concepts/process-model).
   ///
   /// In the case the browser process crashes, both `BrowserProcessExited` and
   /// `ProcessFailed` events are raised, but the order is not guaranteed. These
@@ -408,7 +408,7 @@ namespace Microsoft.Web.WebView2.Core
         /// terminate due to browser process failure or normal shutdown (for example,
         /// when all associated WebViews are closed), after all resources have been
         /// released (including the user data folder). To learn about what these processes
-        /// are, go to [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
+        /// are, go to [Process model](https://learn.microsoft.com/microsoft-edge/webview2/concepts/process-model).
         ///
         /// Multiple app processes can share a browser process by creating their webviews
         /// from a `CoreWebView2Environment` with the same user data folder. When the entire
@@ -429,7 +429,7 @@ namespace Microsoft.Web.WebView2.Core
         /// `ProcessFailed` is raised  for **unexpected** process exits of any kind (browser,
         /// render, GPU, and all other types), or for main frame **render process**
         /// unresponsiveness. To learn more about the WebView2
-        /// Process Model, go to [Process model](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/process-model).
+        /// Process Model, go to [Process model](https://learn.microsoft.com/microsoft-edge/webview2/concepts/process-model).
         ///
         /// In the case the browser process crashes, both `BrowserProcessExited` and
         /// `ProcessFailed` events are raised, but the order is not guaranteed. These

specs/CDPSessionIdSupport.md

@@ -10,8 +10,8 @@ See [DevToolsProtocol Target domain](https://chromedevtools.github.io/devtools-p
 
 The DevToolsProtocol event messages also have sessionId field to indicate which target the event comes from.
 
-However, the current WebView2 DevToolsProtocol APIs like [CallDevToolsProtocolMethod](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2#calldevtoolsprotocolmethod)
-and [DevToolsProtocolEventReceived](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2devtoolsprotocoleventreceivedeventargs)
+However, the current WebView2 DevToolsProtocol APIs like [CallDevToolsProtocolMethod](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2#calldevtoolsprotocolmethod)
+and [DevToolsProtocolEventReceived](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2devtoolsprotocoleventreceivedeventargs)
 don't support sessionId.
 
 To support interaction with different parts of the page, we allow apps to specify a sessionId when calling DevToolsProtocol methods, as well as passing a sessionId to DevToolsProtocol event handlers, with empty string sessionId representing the default target of the top page.

specs/DOMContentLoaded.md

@@ -1,6 +1,6 @@
 # Background
 
-In response to consumers' requests for an event similar to the old [WebView DOMContentLoaded](https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview#mswebviewdomcontentloaded), the WebView2 team has introduced DOMContentLoaded API which indicates that the main DOM elements have finished loading.
+In response to consumers' requests for an event similar to the old [WebView DOMContentLoaded](https://learn.microsoft.com/microsoft-edge/hosting/webview#mswebviewdomcontentloaded), the WebView2 team has introduced DOMContentLoaded API which indicates that the main DOM elements have finished loading.
 In this document we describe the new API. We'd appreciate your feedback.
 
 # Description

specs/DefaultDownloadDialog.md

@@ -11,8 +11,8 @@ position below your button, and alternating open and close calls when the button
 clicked on.
 
 For more complex customizations, you can use the Download APIs -
-[DownloadStarting](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2downloadstartingeventargs?view=webview2-1.0.961.33)
- and [DownloadOperation](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2downloadoperation?view=webview2-1.0.961.33) - to build custom download UI.
+[DownloadStarting](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2downloadstartingeventargs?view=webview2-1.0.961.33)
+ and [DownloadOperation](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2downloadoperation?view=webview2-1.0.961.33) - to build custom download UI.
 
 # Examples
 ```cpp

specs/DisableCrashReporting.md

@@ -98,7 +98,7 @@ interface ICoreWebView2Environment11 : ICoreWebView2Environment10 {
   /// `FailureReportFolderPath` get the folder path of where minidump files is written.
   /// Whenever a WebView2 process crashes, a crash dump file will be created in the crash dump folder.
   /// A crash dump format is minidump files, please see 
-  /// https://docs.microsoft.com/en-us/windows/win32/debug/minidump-files for detailed documentation. 
+  /// https://learn.microsoft.com/windows/win32/debug/minidump-files for detailed documentation. 
   /// Normally when a single child process failed, a minidump will be generated and written to disk, 
   /// then `ProcessFailed` event is raised. But for unexpected crashes, minidump might not be generated 
   /// at all, despite whether `ProcessFailed` event is raised. For times, that there are multiple 

specs/ExecuteScriptWithResult.md

@@ -1,5 +1,5 @@
 # Background
-Our end developers have pointed out gaps in the existing [CoreWebView2.ExecuteScript](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.1150.38#executescript) method, and it is necessary
+Our end developers have pointed out gaps in the existing [CoreWebView2.ExecuteScript](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.1150.38#executescript) method, and it is necessary
 to provide a new method to let our end developers get more information in a more convenient manner.
 The new ExecuteScriptWithResult method will provide exception information if the executed script
 failed, and provides a new method to try to get the script execution result as a string rather than as JSON
@@ -284,7 +284,7 @@ interface ICoreWebView2_10 : ICoreWebView2_9 {
 ```
 
 ## .NET and WinRT
-The documentation for the old interface [CoreWebView2.ExecuteScriptAsync(String) Method](https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.executescriptasync?view=webview2-dotnet-1.0.1150.38#microsoft-web-webview2-core-corewebview2-executescriptasync(system-string)) is here.
+The documentation for the old interface [CoreWebView2.ExecuteScriptAsync(String) Method](https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.executescriptasync?view=webview2-dotnet-1.0.1150.38#microsoft-web-webview2-core-corewebview2-executescriptasync(system-string)) is here.
 ```c#
 namespace Microsoft.Web.WebView2.Core
 {

specs/ExtendedProcessFailed.md

@@ -1,7 +1,7 @@
 # Background
-WebView2 provides applications with the [ProcessFailed](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.705.50#add_processfailed) event so they can react accordingly when a process failure occurs. However, this event does not currently provide additional information about the process failure, nor does it cover the cases in which only subframes within the CoreWebView2 are impacted by the failure, or the cases in which a process other than the browser/render process fails.
+WebView2 provides applications with the [ProcessFailed](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.705.50#add_processfailed) event so they can react accordingly when a process failure occurs. However, this event does not currently provide additional information about the process failure, nor does it cover the cases in which only subframes within the CoreWebView2 are impacted by the failure, or the cases in which a process other than the browser/render process fails.
 
-In this document we describe an extended version of the [PROCESS_FAILED_KIND](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.705.50#corewebview2_process_failed_kind) enum, which covers the new scenarios in which the event is raised: frame-only render process failure, and process failures for processes other than the browser/render process. We also include a new version of the [ProcessFailedEventArgs](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2processfailedeventargs?view=webview2-1.0.705.50) that enables the host application to collect additional information about the process failure for their logging and telemetry purposes.
+In this document we describe an extended version of the [PROCESS_FAILED_KIND](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.705.50#corewebview2_process_failed_kind) enum, which covers the new scenarios in which the event is raised: frame-only render process failure, and process failures for processes other than the browser/render process. We also include a new version of the [ProcessFailedEventArgs](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2processfailedeventargs?view=webview2-1.0.705.50) that enables the host application to collect additional information about the process failure for their logging and telemetry purposes.
 
 The updated API is detailed below. We'd appreciate your feedback.
 
@@ -394,7 +394,7 @@ void WebView_ProcessFailed(object sender, CoreWebView2ProcessFailedEventArgs e)
     bool IsAppContentUri(Uri source)
     {
         // Sample virtual host name for the app's content.
-        // See CoreWebView2.SetVirtualHostNameToFolderMapping: https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.setvirtualhostnametofoldermapping
+        // See CoreWebView2.SetVirtualHostNameToFolderMapping: https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.setvirtualhostnametofoldermapping
         return source.Host == "appassets.example";
     }
 

specs/IFramePermissionRequested.md

@@ -5,7 +5,7 @@ within the iframe are requesting access to priveleged resources. The permission
 request types that we support are: Microphone, Camera, Geolocation,
 Notifications, Other Sensors, and Clipboard Read.
 
-We currently have a [PermissionRequested](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2permissionrequestedeventargs?view=webview2-1.0.1020.30)
+We currently have a [PermissionRequested](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2permissionrequestedeventargs?view=webview2-1.0.1020.30)
 event on our `CoreWebView2` which is raised for any permission requests
 (either from webview or iframes). However, our customers do not have a way to
 determine whether the request has come from the webview or an iframe and

specs/IsPinchZoomEnabled.md

@@ -1,7 +1,7 @@
 # Background
 
 There are two types of zoom in Chromium: Browser Zoom and Pinch-Zoom:
-- Browser zoom, referred to as “Page Zoom” or “Zoom” more generally, is what we get by using Ctrl + +(plus) or – (minus) or Ctrl + Mousewheel. This changes the size of a CSS pixel relative to a device independent pixel and so it will cause page layout to change. End developers can programmatically change browser Zoom properties including [IsZoomControlEnabled](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2settings?view=webview2-1.0.774.44#get_iszoomcontrolenabled) and [ZoomFactor](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2controller?view=webview2-1.0.774.44#get_zoomfactor). Setting ZoomFactor property causes the layout to change and enables scroll bar which lets users interact with the zoomed in content using mouse.
+- Browser zoom, referred to as “Page Zoom” or “Zoom” more generally, is what we get by using Ctrl + +(plus) or – (minus) or Ctrl + Mousewheel. This changes the size of a CSS pixel relative to a device independent pixel and so it will cause page layout to change. End developers can programmatically change browser Zoom properties including [IsZoomControlEnabled](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2settings?view=webview2-1.0.774.44#get_iszoomcontrolenabled) and [ZoomFactor](https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2controller?view=webview2-1.0.774.44#get_zoomfactor). Setting ZoomFactor property causes the layout to change and enables scroll bar which lets users interact with the zoomed in content using mouse.
 - Pinch-zoom, referred to as “Page Scale” zoom, is performed as a post-rendering step, it changes the page scale factor property and scales the surface the web page is rendered onto when user perfoms a pinch zooming action. It does not change the layout but rather changes the viewport and clips the web content, the content outside of the viewport isn't visible onscreen and users can't reach this content using mouse.
 
 Currently, the first type of zoom control is supported in WebView2 and modifying it has no effect on page scale zoom. 

specs/MultiProfile.md

@@ -276,7 +276,7 @@ interface ICoreWebView2Profile3;
 interface ICoreWebView2ControllerOptions : IUnknown {
   /// The `ProfileName` property specifies the profile's name. It has a maximum length of 64 
   /// characters excluding the null terminator and must be a valid file name.
-  /// See [Naming Files, Paths, and Namespaces](https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file)
+  /// See [Naming Files, Paths, and Namespaces](https://learn.microsoft.com/windows/win32/fileio/naming-a-file)
   /// for more information on file names. It must contain only the following ASCII characters:
   ///
   ///  * alphabet characters: a-z and A-Z