diff --git a/microsoft-edge/devtools/console/utilities.md b/microsoft-edge/devtools/console/utilities.md index f0f7ce3570..40c79e7440 100644 --- a/microsoft-edge/devtools/console/utilities.md +++ b/microsoft-edge/devtools/console/utilities.md @@ -28,10 +28,10 @@ ms.date: 11/20/2023 The Console Utilities API contains a collection of convenience variables and functions for performing common tasks, such as: -* Selecting and inspecting DOM elements. -* Displaying data in a readable format. -* Stopping and starting the profiler. -* Monitoring DOM events. +* Selecting and inspecting DOM elements via CSS selectors. +* Displaying data in a readable format. +* Stopping and starting the profiler. +* Monitoring DOM events. These variables and functions only work by entering them directly into the DevTools **Console**; you can't use the variables and call the functions from scripts. diff --git a/microsoft-edge/devtools/network/reference.md b/microsoft-edge/devtools/network/reference.md index c7808cf4a3..de5274be80 100644 --- a/microsoft-edge/devtools/network/reference.md +++ b/microsoft-edge/devtools/network/reference.md @@ -387,7 +387,7 @@ To create a custom throttling profile: A warning (![Throttling warning icon](./reference-images/throttling-warning-icon.png)) icon is displayed in the **Network** tab, to remind you that throttling is enabled. See also: -* [Set up custom network throttling profile](../settings/throttling.md#set-up-a-custom-network-throttling-profile) in _Throttling_. +* [Set up custom network throttling profile](../settings/throttling.md#set-up-a-custom-network-throttling-profile) in _Throttling the CPU or network_. diff --git a/microsoft-edge/devtools/settings/throttling.md b/microsoft-edge/devtools/settings/throttling.md index c82beb6382..4c05fa8e45 100644 --- a/microsoft-edge/devtools/settings/throttling.md +++ b/microsoft-edge/devtools/settings/throttling.md @@ -1,6 +1,6 @@ --- -title: Throttling -description: The Throttling page of DevTools Settings, to control and customize network and CPU speed settings. +title: Throttling the CPU or network +description: Use the Throttling page of DevTools Settings to test a webpage as if using a slower CPU or network. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -21,10 +21,10 @@ ms.date: 06/12/2025 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> -# Throttling - +# Throttling the CPU or network + -In the **Throttling** page of **Customize and control DevTools** (![Customize and control DevTools icon](./throttling-images/customize-and-control-devtools-icon.png)) > **Settings**, you can: +Use the **Throttling** page of DevTools **Settings** to test a webpage as if using a slower CPU or network. In the **Throttling** page of DevTools **Settings**, you can: * Calibrate CPU throttling presets to approximate the typical performance of low- and mid-tier mobile devices. diff --git a/microsoft-edge/devtools/whats-new/2019/12/devtools.md b/microsoft-edge/devtools/whats-new/2019/12/devtools.md index a881cf57f8..0a316ee31a 100644 --- a/microsoft-edge/devtools/whats-new/2019/12/devtools.md +++ b/microsoft-edge/devtools/whats-new/2019/12/devtools.md @@ -334,7 +334,7 @@ In a later release, the **Audits** panel was renamed as the **Lighthouse** panel ###### New configuration UI -The configuration UI has a new, responsive design, and the throttling configuration options have been simplified. For more information on the throttling UI changes, see [Audits Panel Throttling](https://github.com/GoogleChrome/lighthouse/blob/master/docs/throttling.md#devtools-audits-panel-throttling). +The configuration UI has a new, responsive design, and the throttling configuration options have been simplified. For more information on the throttling UI changes, see [Network Throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md). ![The new configuration UI](./devtools-images/start.png) diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml index e391b10cc7..bb42d5c6bd 100644 --- a/microsoft-edge/toc.yml +++ b/microsoft-edge/toc.yml @@ -16,8 +16,9 @@ # bottom leaf nodes # ============================================================================= # top leaf nodes -- name: Microsoft Edge Developer documentation +- name: Microsoft Edge Developer documentation # docset landing page href: developer/index.yml + displayName: landing items: - name: Develop for the web with Microsoft Edge href: ./develop-web-microsoft-edge.md @@ -166,8 +167,9 @@ - name: Microsoft Edge DevTools items: # ----------------------------------------------------------------------------- - - name: Microsoft Edge DevTools documentation - href: ./devtools/landing/index.yml # landing page + - name: Microsoft Edge DevTools documentation # landing page + href: ./devtools/landing/index.yml + displayName: landing # ----------------------------------------------------------------------------- - name: Overview of DevTools href: ./devtools/overview.md @@ -477,7 +479,7 @@ items: - name: Experimental features in Microsoft Edge DevTools href: ./devtools/experimental-features/index.md - displayName: Experimental features, settings + displayName: settings - name: Share a memory trace with more data href: ./devtools/experimental-features/share-memory-traces.md @@ -487,7 +489,7 @@ items: - name: Sample code for DevTools href: ./devtools/samples/index.md - displayName: sample code, demo + displayName: demo # TOOLS ======================================================================= - name: Tools items: @@ -500,7 +502,6 @@ items: - name: Analyze pages using the Inspect tool href: ./devtools/css/inspect.md - displayName: Inspect tool # ----------------------------------------------------------------------------- - name: Device Emulation items: @@ -520,13 +521,11 @@ items: - name: Welcome tool href: ./devtools/welcome/welcome-tool.md - displayName: Welcome tool # ----------------------------------------------------------------------------- - name: Elements tool, for CSS, HTML, and the DOM items: - name: Inspect, edit, and debug HTML and CSS with the Elements tool href: ./devtools/elements-tool/elements-tool.md - displayName: Elements tool - name: DOM items: @@ -568,7 +567,6 @@ - name: Log messages in the Console tool href: ./devtools/console/console-log.md - displayName: Console tool - name: Run JavaScript in the Console href: ./devtools/console/console-javascript.md @@ -576,15 +574,15 @@ - name: Explain Console errors and warnings using Copilot in Edge href: ./devtools/console/copilot-explain-console.md - displayName: Console tool, Copilot in Edge, Copilot, Explain error + displayName: Console tool - name: Console object API Reference href: ./devtools/console/api.md - displayName: Console tool, API Reference + displayName: Console tool - name: Console tool utility functions and selectors href: ./devtools/console/utilities.md - displayName: Console tool, API Reference, DOM selectors + displayName: API Reference, DOM selectors - name: Monitor changes in JavaScript using Live Expressions href: ./devtools/console/live-expressions.md @@ -606,7 +604,7 @@ items: - name: Sources tool overview href: ./devtools/sources/index.md - displayName: Quick source tool, Sources tool # Quick source tool is covered in section "Displaying source files when using a different tool" + displayName: Quick source tool # Quick source tool is covered in section "Displaying source files when using a different tool" - name: Get started debugging JavaScript href: ./devtools/javascript/index.md @@ -735,7 +733,6 @@ - name: Record heap snapshots using the Memory tool ("Heap snapshot" profiling type) href: ./devtools/memory-problems/heap-snapshots.md - displayName: Memory tool - name: Use Allocation instrumentation on timeline ("Allocations on timeline" profiling type) href: ./devtools/memory-problems/allocation-profiler.md @@ -757,7 +754,6 @@ items: - name: Application tool, to manage storage href: ./devtools/storage/application-tool.md - displayName: Application tool - name: View, edit, and delete cookies href: ./devtools/storage/cookies.md @@ -808,7 +804,7 @@ items: - name: Navigate webpage layers, z-index, and DOM using the 3D View tool href: ./devtools/3d-view/index.md - displayName: 3D View tool, composited layers + displayName: composited layers # ----------------------------------------------------------------------------- - name: Animations tool items: @@ -820,13 +816,11 @@ items: - name: Track changes to files using the Changes tool href: ./devtools/changes/changes-tool.md - displayName: Changes tool # ----------------------------------------------------------------------------- - name: Coverage tool items: - name: Find unused JavaScript and CSS code with the Coverage tool href: ./devtools/coverage/index.md - displayName: Coverage tool # ----------------------------------------------------------------------------- - name: Crash analyzer tool items: @@ -837,25 +831,21 @@ items: - name: Optimize CSS styles with the CSS overview tool href: ./devtools/css/css-overview-tool.md - displayName: CSS overview tool # ----------------------------------------------------------------------------- - name: Developer resources tool items: - name: Developer resources tool href: ./devtools/developer-resources/developer-resources.md - displayName: Developer resources tool # ----------------------------------------------------------------------------- - name: Issues tool items: - name: Find and fix problems using the Issues tool href: ./devtools/issues/index.md - displayName: Issues tool # ----------------------------------------------------------------------------- - name: Lighthouse tool # jump page; main article is in Accessibility items: - name: Lighthouse tool href: ./devtools/lighthouse/lighthouse-tool.md - displayName: Lighthouse tool # ----------------------------------------------------------------------------- - name: Media tool items: @@ -867,13 +857,11 @@ items: - name: Inspect a JavaScript ArrayBuffer with the Memory inspector tool # real content pending href: ./devtools/memory-inspector/memory-inspector-tool.md - displayName: Memory inspector tool # ----------------------------------------------------------------------------- - name: Network conditions tool items: - name: Network conditions tool # starter page w/ png and links href: ./devtools/network-conditions/network-conditions-tool.md - displayName: Network conditions tool - name: Override the user agent string href: ./devtools/device-mode/override-user-agent.md @@ -894,13 +882,11 @@ items: - name: Measure runtime performance of a page using the Performance monitor tool href: ./devtools/performance-monitor/performance-monitor-tool.md - displayName: Performance monitor tool # ----------------------------------------------------------------------------- - name: Quick source tool items: - name: Display or edit source files using the Quick source tool href: ./devtools/quick-source/quick-source-tool.md - displayName: Quick source tool # also indexed in "Sources tool overview" # ----------------------------------------------------------------------------- - name: Recorder tool items: @@ -913,7 +899,6 @@ items: - name: Rendering tool, to see what a webpage looks like with different display options or vision deficiencies href: ./devtools/rendering-tools/rendering-tool.md - displayName: Rendering tool - name: Emulate dark or light schemes in the rendered page href: ./devtools/accessibility/preferred-color-scheme-simulation.md @@ -927,31 +912,27 @@ items: - name: Find source files for a page using the Search tool href: ./devtools/search/search-tool.md - displayName: Search tool # ----------------------------------------------------------------------------- - name: Security tool items: - name: Understand security issues using the Security tool href: ./devtools/security/index.md - displayName: Security tool # ----------------------------------------------------------------------------- - name: Sensors tool items: - name: Emulate device sensors href: ./devtools/sensors/index.md - displayName: Device Emulation + displayName: device emulation, device emulator, geolocation, device orientation # ----------------------------------------------------------------------------- - name: Source Maps Monitor tool items: - name: Source Maps Monitor tool href: ./devtools/source-maps-monitor/source-maps-monitor-tool.md - displayName: Source maps monitor tool # ----------------------------------------------------------------------------- - name: WebAudio tool items: - name: WebAudio tool href: ./devtools/webaudio/webaudio-tool.md - displayName: WebAudio tool # ----------------------------------------------------------------------------- - name: WebAuthn tool items: @@ -965,11 +946,9 @@ items: - name: Run commands in the Command Menu href: ./devtools/command-menu/index.md - displayName: Command Menu # ----------------------------------------------------------------------------- - name: Keyboard shortcuts href: ./devtools/shortcuts/index.md - displayName: Keyboard shortcuts # ----------------------------------------------------------------------------- - name: Settings and customization UI items: @@ -983,19 +962,18 @@ - name: Change DevTools language settings href: ./devtools/customize/localization.md - displayName: Settings, Preferences + displayName: preferences - name: Customize keyboard shortcuts href: ./devtools/customize/shortcuts.md - displayName: Settings, Shortcuts + displayName: settings - name: Add custom UI to DevTools using extensions href: ./devtools/customize/extensions.md - displayName: Extensions - - name: Throttling + - name: Throttling the CPU or network href: ./devtools/settings/throttling.md - displayName: Settings + displayName: settings # ----------------------------------------------------------------------------- - name: Remote debugging items: @@ -1028,7 +1006,6 @@ # Inspect tool (distinct from Tools > Inspect tool bucket) - name: Use the Inspect tool to detect accessibility issues by hovering over the webpage href: ./devtools/accessibility/test-inspect-tool.md - displayName: Inspect tool # tests Screen reader support, Keyboard support, Text contrast # ------------------------------------- # Lighthouse tool (distinct from Tools > Lighthouse tool bucket) - name: Test accessibility using Lighthouse # was part of "Accessibility features reference" @@ -1054,15 +1031,12 @@ items: - name: Check for keyboard support by using the Tab and Enter keys href: ./devtools/accessibility/test-tab-enter-keys.md - displayName: keyboard support - name: Analyze the lack of indication of keyboard focus href: ./devtools/accessibility/test-analyze-no-focus-indicator.md - displayName: keyboard focus - name: Analyze keyboard support on forms href: ./devtools/accessibility/test-analyze-no-keyboard-support.md - displayName: keyboard support - name: Test keyboard support using the Source Order Viewer href: ./devtools/accessibility/test-tab-key-source-order-viewer.md @@ -1072,11 +1046,10 @@ items: - name: Test text-color contrast using the Color Picker # was part of "Accessibility features reference" href: ./devtools/accessibility/color-picker.md - displayName: Elements tool, Styles tab, Color Picker + displayName: Elements tool, Styles tab - name: Check text-color contrast in the default state using the Inspect tool href: ./devtools/accessibility/test-inspect-text-contrast.md - displayName: Inspect tool - name: Verify accessibility of all states of elements href: ./devtools/accessibility/test-inspect-states.md @@ -1090,11 +1063,11 @@ items: - name: Test accessibility using the Accessibility tab # was part of "Accessibility features reference" href: ./devtools/accessibility/accessibility-tab.md - displayName: Elements tool, Accessibility tab, screen readers, Accessibility Tree, ARIA attributes, Computed Properties + displayName: Elements tool, screen readers, Accessibility Tree, ARIA attributes, Computed Properties - name: Check the Accessibility Tree for keyboard and screen reader support href: ./devtools/accessibility/test-accessibility-tree.md - displayName: Elements tool, Accessibility tab, screen readers + displayName: Elements tool, Accessibility tab # ------------------------------------- # Rendering tool (distinct from Tools > Rendering tool) - name: Vision deficiencies (Rendering tool) @@ -1133,7 +1106,6 @@ - name: Microsoft Edge DevTools Protocol href: ./devtools/protocol/index.md - displayName: DevTools Protocol - name: Contact the Microsoft Edge DevTools team href: ./devtools/contact.md @@ -1149,7 +1121,7 @@ items: - name: Installing the DevTools extension for Visual Studio Code href: ./visual-studio-code/microsoft-edge-devtools-extension/install.md - displayName: installing, setup + displayName: setup - name: Get started using the DevTools extension for Visual Studio Code href: ./visual-studio-code/microsoft-edge-devtools-extension/get-started.md @@ -1180,7 +1152,7 @@ - name: Update .css files from within the Styles tab (CSS mirror editing) href: ./visual-studio-code/microsoft-edge-devtools-extension/css-mirror-editing-styles-tab.md - displayName: Syncing live changes from the Styles tool by using CSS mirror editing # previous title + displayName: Syncing live changes from the Styles tool by using CSS mirror editing # old title - name: Network tool integration href: ./visual-studio-code/microsoft-edge-devtools-extension/network-tool-integration.md @@ -1214,9 +1186,9 @@ # Microsoft Edge extensions - name: Microsoft Edge extensions items: - - name: Microsoft Edge extensions documentation + - name: Microsoft Edge extensions documentation # landing page href: ./extensions/landing/index.yml - displayName: add-ons, landing + displayName: add-ons, themes, landing - name: Overview of Microsoft Edge extensions href: ./extensions/index.md @@ -1405,7 +1377,7 @@ # Progressive Web Apps - name: Progressive Web Apps items: - - name: Progressive Web Apps (PWAs) documentation + - name: Progressive Web Apps (PWAs) documentation # landing page href: ./progressive-web-apps/landing/index.yml displayName: landing @@ -1502,7 +1474,7 @@ # WebView2 - name: WebView2 items: - - name: WebView2 documentation + - name: WebView2 documentation # landing page href: ./webview2/landing/index.yml displayName: landing @@ -2356,7 +2328,7 @@ - name: Distribute your app and the WebView2 Runtime href: ./webview2/concepts/distribution.md - - name: Enterprise management of WebView2 Runtimes + - name: Enterprise management of WebView2 href: ./webview2/concepts/enterprise.md displayName: Manage WebView2 applications # old title @@ -2366,7 +2338,7 @@ - name: Publish a UWP WebView2 app to the Microsoft Store href: ./webview2/how-to/publish-uwp-app-store.md - displayName: Partner Center, Microsoft Store + displayName: Partner Center # ----------------------------------------------------------------------------- - name: Best practices items: @@ -2599,7 +2571,7 @@ - name: View a JSON file or server response with formatting href: ./web-platform/json-viewer.md - displayName: JSON viewer, view JSON + displayName: JSON viewer - name: Cross-browser API samples href: ./web-platform/samples.md diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md index e92a47e46a..bd283dfdc9 100644 --- a/microsoft-edge/webview2/concepts/distribution.md +++ b/microsoft-edge/webview2/concepts/distribution.md @@ -23,7 +23,7 @@ For introductory information, see [Evergreen vs. fixed version of the WebView2 R #### Servicing the WebView2 Runtime through Windows Server Update Services (WSUS) -See [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2 Runtimes_. +See [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2_. @@ -359,7 +359,7 @@ Example managed app folder structure: * [Prerelease and Release SDKs for WebView2](./versioning.md) * [Feature-detecting to test whether the installed Runtime supports recently added APIs](./versioning.md#feature-detecting-to-test-whether-the-installed-runtime-supports-recently-added-apis) in _Prerelease and Release SDKs for WebView2_. * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md) -* [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2 Runtimes_. +* [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2_. * [Test upcoming APIs and features](../how-to/set-preview-channel.md) * [Prerelease testing using preview channels](../how-to/prerelease-testing.md) * [Self-host by deploying preview channels](../how-to/self-hosting.md) diff --git a/microsoft-edge/webview2/concepts/enterprise.md b/microsoft-edge/webview2/concepts/enterprise.md index 4f33d5e009..26d11fcb18 100644 --- a/microsoft-edge/webview2/concepts/enterprise.md +++ b/microsoft-edge/webview2/concepts/enterprise.md @@ -1,71 +1,83 @@ --- -title: Enterprise management of WebView2 Runtimes -description: How IT admins can manage WebView2 applications and the WebView2 Runtime. +title: Enterprise management of WebView2 +description: How IT Administrators can manage WebView2 applications and the WebView2 Runtime. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article ms.service: microsoft-edge ms.subservice: webview -ms.date: 11/12/2021 +ms.date: 08/21/2026 --- -# Enterprise management of WebView2 Runtimes +# Enterprise management of WebView2 + -This article discusses how IT admins can manage WebView2 applications and the WebView2 Runtime. A developer can integrate the WebView2 component into their app, and then deploy the self-updating Evergreen WebView2 Runtime (along with the app) onto user devices, to power the latest WebView2 features of the app and get the latest security improvements. +IT Admins can use group policy objects (GPO) to configure policy settings for WebView2, to manage WebView2 applications and the WebView2 Runtime. The following policies are relevant to WebView2. -Feedback from IT admins and developers is welcome, through the [WebView2Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo. +Many policies are about updating the WebView2 Runtime. A developer can integrate the WebView2 component into their app, and then deploy the self-updating Evergreen WebView2 Runtime (along with the app) onto user devices, to power the latest WebView2 features of the app and get the latest security improvements. +**Detailed contents:** +* [Update policies](#update-policies) + * [Evergreen Runtime is recommended, rather than a fixed version](#evergreen-runtime-is-recommended-rather-than-a-fixed-version) + * [Rapid response to Chromium vulnerabilities](#rapid-response-to-chromium-vulnerabilities) + * [Microsoft Edge Lifecycle Policy](#microsoft-edge-lifecycle-policy) + * [Suppressing WebView2 Runtime updates (`UpdatesSuppressed`)](#suppressing-webview2-runtime-updates-updatessuppressed) +* [WebView2-specific policies](#webview2-specific-policies) + * [Downgrading the WebView Runtime to an earlier version (`DowngradeVersion`)](#downgrading-the-webview-runtime-to-an-earlier-version-downgradeversion) +* [Browser policies vs. WebView2 policies](#browser-policies-vs-webview2-policies) +* [Windows Server Update Services (WSUS)](#windows-server-update-services-wsus) + * [WebView2 deployment and update using Configuration Manager](#webview2-deployment-and-update-using-configuration-manager) +* [Providing feedback](#providing-feedback) +* [See also](#see-also) - -## Group policies for WebView2 -IT admins can use group policy objects (GPO) to configure policy settings for WebView2. The following policies are relevant to WebView2. + +## Update policies +Microsoft Edge update policies are available for IT Admins to manage the installing and updating aspects of the WebView2 Runtime. The Microsoft Edge browser and WebView2 Runtime are updated using the same update mechanism. - -#### Update policies +A Microsoft Edge update policy applies to both Microsoft Edge and the WebView2 Runtime, unless the policy is channel-specific, such as: +* [Update](/deployedge/microsoft-edge-update-policies#update), in _Microsoft Edge - Update policies_. +* [Update (WebView)](/deployedge/microsoft-edge-update-policies#update-webview), in _Microsoft Edge - Update policies_. -[Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies) are available for IT admins to manage the installing and updating aspects of the WebView2 Runtime. The Microsoft Edge browser and WebView2 Runtime are updated using the same update mechanism. The policy applies to both Microsoft Edge and the WebView2 Runtime, unless the policy is channel-specific, such as [Update](/deployedge/microsoft-edge-update-policies#update) and [Update (WebView)](/deployedge/microsoft-edge-update-policies#update-webview). +To configure update policies for Microsoft Edge and the WebView2 Runtime, see: +* [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge), in the Microsoft Edge Enterprise documentation. -To configure update policies for Microsoft Edge (and the WebView2 Runtime), see [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge), in the Microsoft Edge Enterprise documentation. +See: +* [Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies), in the Microsoft Edge Enterprise documentation. -#### Suppressing WebView2 Runtime updates - -An IT admin can suppress updating of the WebView2 Runtime, if auto-updating needs to be suppressed for a short time. After the time period, updating of the WebView2 Runtime resumes. The [UpdatesSuppressed](/deployedge/microsoft-edge-update-policies#updatessuppressed) policy allows an IT admin to set the time during each day at which to suppress auto-update for both Microsoft Edge and the WebView2 Runtime. This enables an IT admin to configure preferences and proxies once for both the browser and the WebView2 Runtime, to control their network bandwidth and traffic, or for other purposes. - -However, users should not stop updating their WebView2 Runtime; users should not remain on an older version of the WebView2 Runtime. Using older versions of the WebView2 Runtime isn't recommended. Security updates and servicing updates are only available on the latest Stable channel release (Edge Stable) and the latest Beta channel release (Edge Beta). If you use older releases of the Microsoft WebView2 Runtime, you won't receive the latest quality and security updates. - - - -###### Evergreen Runtime is recommended, rather than a fixed version +#### Evergreen Runtime is recommended, rather than a fixed version Using the Evergreen WebView2 Runtime is recommended, unless business-critical requirements necessitate using a fixed version of the WebView2 Runtime. Using the Evergreen WebView2 Runtime: * Helps minimize exposure to known vulnerabilities. * Ensures timely security improvements. * Ensures that WebView2 benefits from continuous security updates that are delivered through Microsoft Edge releases. -For details about security fixes in Microsoft Edge (which apply to WebView2 as well), see [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security), in the Microsoft Edge Enterprise documentation. - -See also: +See: * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md) +For details about security fixes in Microsoft Edge (which also apply to WebView2), see: +* [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security), in the Microsoft Edge Enterprise documentation. - -###### Rapid Response to Chromium vulnerabilities -To help maintain a secure browsing environment, Microsoft Edge addresses Chromium engine-level vulnerabilities soon after the vulnerabilities are disclosed. + +#### Rapid response to Chromium vulnerabilities -Security fixes address vulnerabilities such as: +To help maintain a secure browsing environment, Microsoft Edge addresses vulnerabilities in the Chromium browser engine soon after the vulnerabilities are disclosed. +Security fixes in the Chromium browser engine address vulnerabilities such as: * **Remote code execution** – Mitigates risks of arbitrary code execution via malicious content. * **Privilege escalation** – Reduces chances of unauthorized system access. * **Information disclosure and spoofing** – Protects sensitive data, and helps prevent phishing attacks. +For details about security fixes in Microsoft Edge (which also apply to WebView2), see: +* [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security), in the Microsoft Edge Enterprise documentation. - -###### Microsoft Edge Lifecycle Policy + + +#### Microsoft Edge Lifecycle Policy Microsoft WebView2 follows the Modern Lifecycle Policy. @@ -75,25 +87,56 @@ See: -#### Browser policies +#### Suppressing WebView2 Runtime updates (`UpdatesSuppressed`) + +An IT Admin can suppress updating of the WebView2 Runtime, if auto-updating needs to be suppressed for a short time. After the time period, updating of the WebView2 Runtime resumes. The `UpdatesSuppressed` policy allows an IT Admin to set the time during each day at which to suppress auto-update for both Microsoft Edge and the WebView2 Runtime. This enables an IT Admin to configure preferences and proxies once for both the browser and the WebView2 Runtime, to control their network bandwidth and traffic, or for other purposes. + +However, users should not stop updating their WebView2 Runtime; users should not remain on an older version of the WebView2 Runtime. Using older versions of the WebView2 Runtime isn't recommended. Security updates and servicing updates are only available on the latest Stable channel release (Edge Stable) and the latest Beta channel release (Edge Beta). If you use older releases of the Microsoft WebView2 Runtime, you won't receive the latest quality and security updates. + +See: +* [UpdatesSuppressed](/deployedge/microsoft-edge-update-policies#updatessuppressed), in _Microsoft Edge - Update policies_. + -[Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) doesn't apply to WebView2 applications. This is by design, because apps and browsers have different use cases, and IT admins might not be aware of what applications use WebView2. + +## WebView2-specific policies + +Policies that are specific to the WebView2 Runtime are available to the IT Admin, to manage the WebView2 Runtime directly. In most cases, we recommend that the WebView2 app developer implement their own group policies to manage the use of the WebView2 Runtime, because it's easier for the IT Admin to manage a WebView2 _app_, rather than managing the WebView2 _Runtime_ directly. -Applying browser policies on WebView2 would have unintended consequences. For example, IT admins can block JavaScript in the browser, and that would break WebView2 apps that use JavaScript. To prevent that, browser policies are separate from WebView2 policies. +See: +* [Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies), in the Microsoft Edge Enterprise documentation. -#### WebView2-specific policies +#### Downgrading the WebView Runtime to an earlier version (`DowngradeVersion`) -[Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies) are available to for you to manage WebView2 directly. However, we recommend that WebView2 app developers implement their own group policies to manage the use of WebView2, because it's easier for administrators to manage the app instead of managing WebView2 directly. +Enterprise Downgrade is a temporary, IT Admin-controlled capability that allows a specific WebView2 app to revert to using an earlier version of the WebView2 Runtime, if there's a critical regression in the WebView2 app when using the latest version of the WebView2 Runtime. + +The Enterprise Downgrade feature is controlled via the `DowngradeVersion` policy. + +See: +* [Downgrade the WebView2 Runtime to an earlier version](/deployedge/webview2-downgrade-runtime), in the Microsoft Edge Enterprise documentation. +* [DowngradeVersion](/deployedge/microsoft-edge-webview-policies#downgradeversion) in _Microsoft Edge WebView2 - Policies_. + + + +## Browser policies vs. WebView2 policies + +Browser policies are separate from WebView2 policies. Policies for Microsoft Edge don't apply to the WebView2 Runtime and WebView2 apps. This is by design, because apps and browsers have different use cases, and an IT Admin might not know which apps use WebView2. + +Applying browser policies on the WebView2 Runtime would have unintended consequences. For example, the IT Admin can block JavaScript in the browser, and that would break WebView2 apps that use JavaScript. To prevent that, browser policies are separate from WebView2 policies. + +See: +* [Microsoft Edge - Policies](/deployedge/microsoft-edge-policies), in the Microsoft Edge Enterprise documentation. +* [Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies), in the Microsoft Edge Enterprise documentation. ## Windows Server Update Services (WSUS) -Windows Server Update Services (WSUS) enables IT admins to deploy the latest Microsoft product updates. You can use WSUS to fully manage the distribution of updates of WebView2 that are released through Microsoft Update to computers on your network. +Windows Server Update Services (WSUS) enables IT Admins to deploy the latest Microsoft product updates. You can use WSUS to fully manage the distribution of updates of WebView2 that are released through Microsoft Update to computers on your network. -See [Windows Server Update Services (WSUS) overview](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus). +See: +* [Windows Server Update Services (WSUS) overview](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) The recommended way of receiving WebView2 updates is by using the default Microsoft Edge updater. Any modification of update and servicing paths should be done with caution. @@ -104,7 +147,17 @@ The recommended way of receiving WebView2 updates is by using the default Micros In Configuration Manager, WebView2 options exist under the **Microsoft Edge Management** node. -See [Update Microsoft Edge](/intune/configmgr/apps/deploy-use/deploy-edge#update-microsoft-edge) in _Microsoft Edge Management_, in the App management documentation. +See: +* [Update Microsoft Edge](/intune/configmgr/apps/deploy-use/deploy-edge#update-microsoft-edge) in _Microsoft Edge Management_, in the App management documentation. + + + +## Providing feedback + +Feedback from IT Admins and developers is welcome, through the [WebView2Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo. + +See also: +* [Contact the WebView2 team](../contact.md) @@ -112,6 +165,7 @@ See [Update Microsoft Edge](/intune/configmgr/apps/deploy-use/deploy-edge#update * [Distribute your app and the WebView2 Runtime](./distribution.md) - Evergreen vs. fixed version of the WebView2 Runtime. +* [Contact the WebView2 team](../contact.md) Microsoft Edge Enterprise documentation: @@ -119,12 +173,14 @@ Microsoft Edge Enterprise documentation: * [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule) * [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security) * [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge) +* [Downgrade the WebView2 Runtime to an earlier version](/deployedge/webview2-downgrade-runtime) * [Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) * [Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies) * [Update](/deployedge/microsoft-edge-update-policies#update) * [UpdatesSuppressed](/deployedge/microsoft-edge-update-policies#updatessuppressed) * [Update (WebView)](/deployedge/microsoft-edge-update-policies#update-webview) * [Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies) + * [DowngradeVersion](/deployedge/microsoft-edge-webview-policies#downgradeversion) Modern Lifecycle Policy documentation: * [Modern Lifecycle Policy](/lifecycle/policies/modern) diff --git a/microsoft-edge/webview2/concepts/measures.md b/microsoft-edge/webview2/concepts/measures.md index aa0523b020..7a999f1b7a 100644 --- a/microsoft-edge/webview2/concepts/measures.md +++ b/microsoft-edge/webview2/concepts/measures.md @@ -160,7 +160,7 @@ See: Restore default Access Control Lists (ACLs). See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) @@ -171,7 +171,7 @@ Don't modify the default Access Control Lists (ACLs) that Windows sets on the We If security tools modify the ACLs on WebView2 Runtime folders, these sandboxed processes might lose the permissions they need to read and execute the Runtime binaries, which can cause blank screens, initialization failures, or crashes. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) @@ -184,7 +184,7 @@ A Low Integrity Level process (LowIL) must be able to Read and Execute the WebVi _Low Integrity Level (LowIL)_ is a Windows security mechanism that restricts a process's ability to write to higher-integrity objects (such as most user-profile and system locations). WebView2 renderer processes run at Low IL to reduce the impact of a compromised process. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) @@ -357,7 +357,7 @@ Tune scanning with scoped exclusions for the WebView2 Runtime directory and user Avoid broad, global exclusions. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) * [Manage user data folders](./user-data-folder.md) @@ -445,7 +445,7 @@ Ensure that authentication endpoints and Content Delivery Network (CDN) endpoint Validate authentication endpoints and Content Delivery Network (CDN) endpoints. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) @@ -460,7 +460,7 @@ Microsoft Edge servicing updates the following versioned subfolders: `C:\Program Files (x86)\Microsoft\EdgeWebView\Application\\` See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md) * [Distribute your app and the WebView2 Runtime](./distribution.md) @@ -483,7 +483,7 @@ Issue: The app works only at higher privilege. The app fails in the following e Keep default `ALL APPLICATION PACKAGES` permissions on WebView2 Runtime directories; a Low integrity level process (LowIL) must **read/execute**. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) This includes the Evergreen WebView2 Runtime path under `C:\Program Files (x86)\Microsoft\EdgeWebView\Application\\`, which must retain `ALL APPLICATION PACKAGES` Read/Execute permissions. @@ -655,7 +655,7 @@ Child processes include: Do not end Crashpad or Graphics Processing Unit (GPU) processes, because they're crucial for stability and rendering. See: -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) * [Handling process-related events in WebView2](./process-related-events.md) @@ -683,7 +683,7 @@ See: * [Handling process-related events in WebView2](./process-related-events.md) * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md) * [Distribute your app and the WebView2 Runtime](./distribution.md) -* [Enterprise management of WebView2 Runtimes](./enterprise.md) +* [Enterprise management of WebView2](./enterprise.md) * [Process model for WebView2 apps](./process-model.md) * [Manage user data folders](./user-data-folder.md) diff --git a/microsoft-edge/webview2/landing/index.yml b/microsoft-edge/webview2/landing/index.yml index 355207a3b5..50b3b95204 100644 --- a/microsoft-edge/webview2/landing/index.yml +++ b/microsoft-edge/webview2/landing/index.yml @@ -245,7 +245,7 @@ landingContent: - text: Distribute your app and the WebView2 Runtime url: ../concepts/distribution.md - - text: Enterprise management of WebView2 Runtimes + - text: Enterprise management of WebView2 url: ../concepts/enterprise.md - text: Distribute an app as a single executable file diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md index dcb55cce80..7dec4c356f 100644 --- a/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md +++ b/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md @@ -27,7 +27,7 @@ This Prerelease version of the WebView2 SDK requires Microsoft Edge version 86.0 #### Features -* Added [WebView2 Group Policies](/deployedge/microsoft-edge-webview-policies). For best practices, see [group policies for WebView2](../../concepts/enterprise.md#group-policies-for-webview2). +* Added [WebView2 Group Policies](/deployedge/microsoft-edge-webview-policies). For best practices for using group policies, see [Enterprise management of WebView2](../../concepts/enterprise.md). * > [!IMPORTANT] > **Breaking Change**: Deprecated the old registry location.