Utbildning
Utbildningsväg
Use advance techniques in canvas apps to perform custom updates and optimization - Training
Use advance techniques in canvas apps to perform custom updates and optimization
Experimental features in Microsoft Edge DevTools
Microsoft Edge DevTools provide access to experimental features that are still in development. This article lists and describes the experimental features that are in either:
- The latest version of the Canary preview channel of Microsoft Edge.
- The latest version of the Stable release of Microsoft Edge.
All channels of Microsoft Edge have experimental features. You can get the latest experimental features by using the Microsoft Edge Canary channel. To view the full list of experiments that are available in your version of Microsoft Edge, see the Settings > Experiments page in DevTools.
These experiments could be unstable or unreliable and may require you to restart DevTools.
The following experimental features are turned on by default. You can use these features right away, without changing any settings. You can turn off these default experimental features, if needed.
Turned on by default in Microsoft Edge Canary 135:
- Enable full accessibility tree view in the Elements panel
- Redesign of the filter bar in the Network panel
- Autofill panel
- Performance panel: enable dimming unrelated events in performance insights and search results
- Performance panel: enable a switch to an alternative timeline navigation option
- Performance panel: enable third party dependency features
- Enable webhint
- Show issues in Elements
- Open source files in Visual Studio Code
Turned on by default in Microsoft Edge Stable 133:
- Redesign of the filter bar in the Network panel
- Autofill panel
- Performance panel: enable a switch to an alternative timeline navigation option
- Enable webhint
- Show issues in Elements
- Open source files in Visual Studio Code
Experimental features are constantly being updated and might cause performance issues. This is one reason you might want to turn off an experiment.
To turn an experiment on or off in Microsoft Edge:
To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.
In DevTools, on the main toolbar, click the Customize and control DevTools (
) button, and then click the Settings (
) button. Or, press Shift+?.On the left side of the Settings panel, select the Experiments page:
Select or clear the checkbox for an experiment. Some experiments are selected by default.
Click Close (
) in the upper right of DevTools Settings.Click the Reload DevTools button.
To restore the default settings for which experimental features are turned on:
To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.
In DevTools, on the main toolbar, click the Settings (
) button. Or, press Shift+?. The Settings panel opens, with the Preferences page selected.At the bottom of the Preferences page, click the Restore defaults and refresh button, and then click Close (
).
You can filter the experimental features by text included in the title.
To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.
In DevTools, on the main toolbar, click the Settings (
) button. Or, press Shift+?. The Settings panel opens, with the Preferences page selected.On the left side of the Settings panel, select the Experiments page.
Click in the Filter text box and enter text, such as timeline. As you type, only the matching checkboxes are shown in the Experiments page.
To end filtering, clear the Filter text box.
We're eager to hear your feedback about experimental features. To share feedback with us, Contact the Microsoft Edge DevTools team.
The experiments checkboxes that appear in the latest version of the Canary preview channel of Microsoft Edge are listed below. The Stable release is also noted, following behind the addition or removal of checkboxes in Canary.
To capture JavaScript stack traces when DOM nodes are added to the DOM at runtime, enable this experiment. This experiment adds the Stack Trace tab in the Elements tool, grouped with the Styles tab:
After you enable the experiment, you can test it as follows:
- In a new window or tab, open a webpage that creates DOM nodes dynamically via JavaScript, such as the TODO demo app.
- In the rendered demo page, create a new todo item.
- In the rendered demo page, right-click the new todo item, and then select Inspect. DevTools opens, showing the Elements tool.
- Click the Stack Trace tab, which is grouped with the Styles tab.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Makes the Protocol monitor tool available in DevTools:
The Protocol monitor tool displays the messages that are sent and received by DevTools, to debug the inspected page. DevTools communicates with the inspected page by using the Chrome DevTools Protocol (CDP).
To select this checkbox and then open the Protocol monitor tool:
Select this Protocol Monitor checkbox as described in Turning an experiment on or off, above.
In Quick View at the bottom of DevTools, click the More tools (+) button, and then select Protocol monitor.
Or, open the Command Menu, such as by pressing Ctrl+Shift+P (Windows/Linux) or Command+Shift+P (macOS), and then type protocol in the text box. Then select Show Protocol monitor.
The Protocol monitor tool is displayed in the Quick View panel at the bottom of DevTools.
See also:
- Use the Chrome DevTools Protocol (CDP) in WebView2 apps
- [Experimental] Protocol monitor in What's New In DevTools (Chrome 92).
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 105
Whether to display a checkbox to expose internals in heap snapshots in the Memory tool.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Enable new Advanced Perceptual Contrast Algorithm (APCA) replacing previous contrast ratio and AA/AAA guidelines
The Advanced Perceptual Contrast Algorithm (APCA) replaces the AA/AAA guidelines contrast ratio in the Color Picker. The Color Picker is used in the Styles tab in the Elements tool.
APCA is a new way to compute contrast. It is based on modern research on color perception. Compared to AA/AAA guidelines, APCA is more context-dependent. The contrast is calculated based on the following spatial properties of the text, color, and context.
- Spatial properties of text that include font weight and size.
- Spatial properties of color that include perceived contrast between text and background.
- Spatial properties of context that include ambient light, surroundings, and intended purpose.
See also:
- New color contrast calculation - Advanced Perceptual Contrast Algorithm (APCA) in What's New in DevTools (Microsoft Edge 89).
- Change colors with the Color Picker in CSS features reference.
- Test text-color contrast using the Color Picker
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Adds a Switch to Accessibility Tree view button in the Elements tool that toggles between the DOM tree and the accessibility tree. The button label toggles to Switch to DOM Tree view.
If this Experiment checkbox is cleared, the Elements tool lacks the button:
If this Experiment checkbox is selected, the Elements tool has the button:
The Accessibility Tree view in the Elements tool:
See also:
- Test accessibility using the Accessibility tab
- Full accessibility tree view in the Elements tool in What's New in DevTools (Microsoft Edge 90).
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
You can use the visual Font Editor to edit fonts. Use it define fonts and font characteristics. The visual Font Editor helps you do the following:
- Switch between units for different font properties
- Switch between keywords for different font properties
- Convert units
- Generate accurate CSS code
To use the visual Font Editor:
To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.
In DevTools, on the main toolbar, select the Elements tab. If the Elements tab isn't visible, click the More tabs (
) button, or else the More Tools (
) button.In the Styles tab, select the Font Editor icon.
Some browser channels have the checkbox label Enable new Font Editor tool within the Styles pane.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- Checkbox label in Canary 135: Enable new font editor within the Styles tab
- This checkbox is present in Microsoft Edge Stable 133.
- Checkbox label in Stable 133: Enable new font editor within the Styles Pane
Enables automatic contrast issue reporting in the Issues tool.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Enables experimental cookie features.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Not applicable for Microsoft Edge. Selecting or clearing this checkbox has no effect.
Status:
- This checkbox is not present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Whether to sync CSS changes in the Styles tab in the Elements tool.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 106
Highlights a violating node or attribute in the Elements tool's DOM tree.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 104
Controls whether to group resources into separate Authored and Deployed trees in the Page tab of the Sources tool. This feature in the Sources tool allows you to group source files in two folders depending on whether these are:
- Original source files (authored, that is, files with your local edits).
- Production files (deployed files that are on the web server after compiling and bundling the source files).
See also:
- Using the Page tab to explore resources that construct the current webpage in Sources tool overview.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 106
In the Sources tool's tree view, omits code that's included in the Ignore list.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 120
In the Network tool, the filter bar has been redesigned:
- The buttons are replaced by a Request types dropdown list.
- The checkboxes are replaced by a More filters dropdown list.
Filter bar with this checkbox cleared:
Filter bar with this checkbox selected:
See also:
- Filter resources in Inspect network activity.
- Filter requests in Network features reference.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 125
Adds an Autofill tool to DevTools, to record various events that the browser triggers when a user is filling in a form by using the browser's autofill feature. For example, when the browser remembers your address and autofills it in an address field.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 124
This experiment improves the Performance tool's Main section to help you quickly identify postMessage events and handlers, by distinguishing events that are triggered by the postMessage method from other events that are displayed in the Performance tool. This experiment helps you investigate performance issues that are related to posting messages across various threads of an application, to view messages between windows, iframes, and dedicated workers.
Without this experiment, events that are triggered by dispatching and handling messages between threads of an application appear as generic scripting function-call events. With this experiment enabled:
postMessagedispatch events appear as Schedule postMessage.postMessagehandler events appear as On Message:
This experiment helps you investigate when a postMessage call occurred, and how long the message was queued before the postMessage handler starts. The dispatch events are linked to handler events by initiator arrows that appear when you click on either type of event:
See also:
- View messages between windows, iframes, and dedicated workers in Performance features reference.
- Performance recording event reference
- postMessage Trace Events demo (rendered)
- postMessage Trace Events demo (source code)
- postMessage events and handlers are distinguished from other events in What's New in DevTools (Microsoft Edge 124).
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge Stable 129
Shows a Server Timings track in the Main section of the Performance tool, to display server timing events sent by your HTTP server. To learn more, see Server timing at MDN Web Docs.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge Canary 133
Enables additional insights within the Insights side panel.
To use this experiment, first select the Performance panel: enable performance insights checkbox, and then, if you want to see even more insights, also select the Performance panel: enable experimental performance insights checkbox.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge Canary 133
This experiment changes the color of certain events in the main section of the Performance tool to gray. This happens in two cases:
When you search for an event by using Ctrl+F and then type text, only the search matches retain their coloring; the other events turn gray.
When you use the Insights side-panel, and expand one of the insights, only the events that are related to that insight retain their coloring; the other events turn gray.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge Canary 133
Adds a Show shortcuts (
) button in the Performance tool's toolbar that enables you to select Classic or Modern keyboard navigation of the timeline.
In Microsoft Edge 133 or later, select this experiment checkbox, close Settings, and then click the Restart DevTools button.
In DevTools, in the Performance tool, record a profile.
The Show shortcuts (
) button is displayed in the upper right of the Performance tool, below the Help (
) button for DevTools.Click the Show shortcuts (
) button.The Keyboard shortcuts popup dialog opens.
With Classic selected:
With Modern selected:
Select the Classic or Modern option button.
The list of keyboard shortcuts changes to relect Classic or Modern keyboard navigation of the timeline.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge Canary 134
Includes a Dim 3rd Parties checkbox in the Performance tool to "dim" the performance events that come from third-party dependencies. For example, if your code uses the React library, checking the Dim 3rd Parties checkbox greys-out and dims the React events in a profile.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is not present in Microsoft Edge Stable 133.
Controls whether to log DevTools uncaught exceptions in the Console tool.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
webhint is an open-source tool that provides real-time feedback for websites and local webpages. The type of feedback provided by webhint includes:
- Accessibility
- Cross-browser compatibility
- Security
- Performance
- Progressive Web Apps (PWAs)
- Other common web development issues
The webhint experiment displays webhint feedback in the Issues tool. Select an issue to display documentation about the solution and a list of the affected resources on your website. Select a resource link to open the relevant tool, such as Network, Sources, or Elements:
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Displays syntax errors as wavy underlines under DOM nodes in the Elements tool.
See also:
- Wavy underlines highlight code issues and improvements in Elements tool in What's New in DevTools (Microsoft Edge 91).
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
The Open source files in Visual Studio Code experiment replaces the code editor of the Sources tool with Visual Studio Code, for editing local files. When you turn on this experiment, Developer Tools detects when you edit a local file, and prompts you to select a folder to use as your Workspace.
When you select a folder to use as your Workspace, selecting any link to a file in DevTools opens the file in Visual Studio Code. In previous versions of Microsoft Edge, this action opened the file in the code editor of the Sources tool in DevTools.
Any edits that you make in DevTools now change the file on the hard drive and sync live with Visual Studio Code.
See also:
- Opening source files in Visual Studio Code - setting up your workspace.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 114
Enables Adaptive CPU throttling.
See also:
- Throttle the CPU while recording in Performance features reference.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Enables using Copilot in the Microsoft Edge Sidebar to explain HTML elements and CSS styles to help you better understand a particular element or style rule that's displayed in the Elements tool. To ask Copilot about an element or style rule, click the Copilot button next to it, and then ask follow-up questions.
This experiment is not available when the Sidebar is turned off.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Controls whether to live-update the heap profile.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Controls whether to show the sampling heap profiler timeline in the Performance tool.
See also:
- Introduction to the Performance tool
- Record heap snapshots using the Memory tool ("Heap snapshot" profiling type)
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Adds an Invalidations section for Recalculate Style events in the Summary tab of the Performance tool. The Invalidations section provides information about the root cause for a Recalculate Style event, which might be helpful when investigating long-running Recalculate Style events that are causing performance issues.
The Invalidations section lists the DOM nodes that were invalidated as a result of a change on the webpage, such as a DOM mutation, and which the browser engine had to restyle during the Recalculate Style event.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Controls whether to show all events in the Performance tool.
See also:
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 128
This experiment makes the Performance tool capture newly added traces, to support enhanced traces v2. This feature is being implemented in the upstream Chromium project. This experiment doesn't affect the capabilities of Microsoft Edge to capture enhanced traces and doesn't impact DevTools user's experience.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
See also:
- Share enhanced performance and memory traces
- Performance features reference
- Performance recording event reference
new as of Microsoft Edge 128
In the Performance tool, when exporting the trace file, stores the source code of compiled scripts in the trace file.
This experiment makes the Performance tool record script source text in traces. This feature is being implemented in the upstream Chromium project.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
See also:
- Share enhanced performance and memory traces
- Performance features reference
- Performance recording event reference
new as of Microsoft Edge 128
Adds a Trace Event section to the Summary tab of the Performance tool. The Trace Event section is displayed when you select an event in a recorded performance trace. The Trace Event section displays debugging information about the selected trace event, such as its name and duration.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
See also:
- Share enhanced performance and memory traces
- Performance features reference
- Performance recording event reference
Whether to halt at test breakpoints. This experiment makes breakpoints more reliable.
See also:
- Enable synchronization on instrumentation breakpoints
- The first time source files are loaded, breakpoints might not trigger
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
new as of Microsoft Edge 118
Whether to use scope information from source maps.
See also:
- Map the processed code to your original source code, for debugging
- Mapping minified code to your source code to show readable code in Sources tool overview.
Status:
- This checkbox is present in Microsoft Edge Canary 135.
- This checkbox is present in Microsoft Edge Stable 133.
Ytterligare resurser
Dokumentation
-
What's New in DevTools (Microsoft Edge 131) - Microsoft Edge Developer documentation
Can disable Edge experiment settings. View CSS selector stats information in Insights tab of sidebar panel in Performance tool. Fixed edit field to exit after pressing tab after auto-completion. Removed Visual Studio Code themes. And more.
-
Microsoft Edge DevTools documentation - Microsoft Edge Developer documentation
Development using DevTools in Microsoft Edge.
-
About the list of tools - Microsoft Edge Developer documentation
About the list of tools in DevTools.