Microsoft Edge Blocking Chrome



  1. Microsoft Blocking Google
  2. Microsoft Edge Blocking Chrome
  3. Does Microsoft Edge Block Google Chrome

Chrome: Microsoft's Tracking Prevention hits Google the hardest. The new Edge browser, built on the same open source code as Google Chrome, contains a new Tracking Prevention feature that.

-->

Announcements from the Microsoft Edge DevTools team

The following sections are a list of announcements you may have missed from the Microsoft Edge DevTools team. Check out the announcements to try new features in the DevTools, Microsoft Visual Studio Code extensions, and more. To stay up to date on all the latest and greatest features in your developer tools, download the Microsoft Edge preview channels and follow us on Twitter.

Use the DevTools in Windows high contrast mode

The Microsoft Edge DevTools are now displayed in high contrast mode when Windows is in high contrast mode.

Follow the instructions to turn on high contrast mode in Windows. To open the DevTools in Microsoft Edge, select F12 or Ctrl+Shift+I. The DevTools are displayed in high contrast mode.

Note

The Microsoft Edge DevTools currently support high contrast mode on Windows but not on macOS.

Chromium issue #1048378

  • The new Microsoft Edge is powered by Chromium, meaning it can run extensions designed for Google Chrome. These extensions seem to run without issue, and that might be a concern for Google.
  • Microsoft Edge is getting a new “performance mode” which will give it a boost over rival browsers like Google Chrome and Mozilla Firefox. This performance mode will automatically optimize your.
Microsoft edge blocks chrome install

Match keyboard shortcuts in the DevTools to Visual Studio Code

From your feedback and the Chromium public issue tracker, the Microsoft Edge DevTools team learned that you wanted the ability to customize keyboard shortcuts in the DevTools. In Microsoft Edge 84, you are now able to match keyboard shortcuts in the DevTools to Visual Studio Code, which is just one of the features the team is working on for shortcut customization.

To try the experiment, open DevTools Settings by selecting ? or choosing the icon in the top-right corner of the DevTools. Navigate to the Experiments section and check Enable custom keyboard shortcuts settings tab (requires reload). Now reload the DevTools, open Settings again, and navigate to the Shortcuts section.

Choose DevTools (Default) in the Match shortcuts from preset dropdown and select Visual Studio Code. The keyboard shortcuts in the DevTools now match the shortcuts for equivalent actions in Visual Studio Code.

For example, the keyboard shortcut for pausing or continuing running a script in Visual Studio Code is F5. With the DevTools (Default) preset, that same shortcut in the DevTools is F8 but with the Visual Studio Code preset, that shortcut is now also F5.

The feature is currently available in Microsoft Edge 84 as an experiment, so please share your feedback with the team!

Chromium issue #174309

Remote debug Surface Duo emulators

You are now able to remotely debug your web content running in the Surface Duo emulator using the full power of the Microsoft Edge DevTools.

With the Surface Duo emulator, you are able to test how your web content renders on a new class of foldable and dual-screen devices. The emulator runs the Android operating system and provides the Microsoft Edge Android app. Load your web content in the Microsoft Edge app and debug it with the Microsoft Edge DevTools.

Microsoft Edge Blocking Chrome

The edge://inspect page in a desktop instance of Microsoft Edge shows the SurfaceDuoEmulator with a list of the open tabs or PWAs that are running on the Surface Duo emulator.

Choose inspect for the tab or PWA that you want to debug to open the Microsoft Edge DevTools. Follow the step-by-step guide to remotely debug your web content on the Surface Duo emulator.

Resize the DevTools drawer more easily

In Microsoft Edge 83 or earlier, you were only able to resize the DevTools Drawer by hovering inside the toolbar of the Drawer. The Drawer behaved differently than the other resize controls for panes in the DevTools where you hover on the border of the pane to resize it. Choose the following image to display how resizing the Drawer worked in version 83 or earlier of Microsoft Edge.

Starting with Microsoft Edge 84, you are now able to resize the Drawer by hovering over the border of the Drawer. This change aligns the behavior resizing the DevTools Drawer with the way you resize other panes in the DevTools. Choose the following image to display resizing in action in Microsoft Edge 84.

Chromium issue #1076112

Screencasting navigation buttons display focus

When remote debugging an Android device, a Windows 10 device, or a Surface Duo emulator, you are able to toggle screencasting with the icon in the top-left corner of the DevTools. With screencasting enabled, you are able to navigate the tab in Microsoft Edge on the remote device from the DevTools window. In Microsoft Edge 84, these navigation buttons are now also keyboard accessible.

Chromium issue #1081486

Network panel Details pane is now accessible

In Microsoft Edge 84, the Details pane in the Network tool now takes focus when you open it for a resource in the Network Log. This change allows screen readers to read out and interact with the content of the Details pane.

Chromium issue #963183

Announcements from the Chromium project

The following sections announce additional features available in Microsoft Edge 84 that were contributed to the open source Chromium project.

Fix site issues with the new Issues tool in the DevTools Drawer

The new Issues tool in the DevTools Drawer was built to help reduce the notification fatigue and clutter of the Console. Currently, the Console is the central place for website developers, libraries, frameworks, and Microsoft Edge to log messages, warnings, and errors. The Issues tool aggregates warnings from the browser in a structured, aggregated, and actionable way, links to affected resources within Microsoft Edge DevTools, and provides guidance on how to fix the issues. Over time, more and more warnings are surfaced in Microsoft Edge in the Issues tool rather than the Console, which should help reduce the clutter in the Console.

To get started, navigate to Find And Fix Problems With The Microsoft Edge DevTools Issues tool.

Chromium issue #1068116

View accessibility information in the Inspect Mode tooltip

The Inspect Mode tooltip now indicates whether the element has an accessiblename and role and is keyboard-focusable.

Chromium issue #1040025

Performance panel updates

View Total Blocking Time information in the footer

After recording your load performance, the Performance panel now shows Total Blocking Time (TBT) information in the footer. TBT is a load performance metric that helps quantify how long a page takes to become usable. It essentially measures how long a page appears to be usable (because the content is rendered to the screen); but is not actually usable, because JavaScript is blocking the main thread and therefore the page does not respond to user input. TBT is the main metric for approximating First Input Delay.

Microsoft Edge Blocking Chrome

To get Total Blocking Time information, do not use the Refresh Page workflow for recording page load performance.

Instead, select Record , manually reload the page, wait for the page to load, and then stop recording.

If Total Blocking Time: Unavailable is displayed, Microsoft Edge DevTools did not get the required information from the internal profiling data in Microsoft Edge.

Chromium issue #1054381

Layout Shift events in the new Experience section

The new Experience section of the Performance panel helps you detect layout shifts. Cumulative Layout Shift (CLS) is a metric that helps you quantify unwanted visual instability.

Choose the Layout Shift event to display the details of the layout shift in the Summary pane. Hover on the Moved from and Moved to fields to visualize where the layout shift occurred.

More accurate promise terminology in the Console

Microsoft Blocking Google

When logging a Promise, the Console incorrectly provided PromiseStatus value set to resolved.

The Console now uses the term fulfilled, which aligns with the Promise specification. For more information about the Promise specification, navigate to States and Fates on GitHub.

V8 issue #6751

Styles pane updates

Chrome

Support for the revert keyword

The autocomplete UI of the Styles pane now detects the revert CSS keyword, which reverts the cascaded value of a property to the previous value applied to the styling of the element.

Chromium issue #1075437

Image previews

Hover on a background-image value in the Styles pane to display a preview of the image in a tooltip.

Chromium issue #1040019

Color Picker now uses space-separated functional color notation

CSS Color Module Level 4 specifies that color functions, such as rgb(), should support space-separatedarguments. For example, rgb(0, 0, 0) is equivalent to rbg(0 0 0).

When you choose colors with the Color Picker or alternate between color representations in the Styles pane by holding Shift and selecting the background-color value, the space-separated argument syntax is displayed.

You should also display the syntax in the Computed pane and the Inspect Mode tooltip.

Microsoft Edge DevTools is using the new syntax because upcoming CSS features such as color() do not support the deprecated comma-separated argument syntax.

The space-separated argument syntax has been supported in most browsers for a while. For more information, navigate to Can I use: Space-separated functional color notations?

Chromium issue #1072952

Deprecation of the Properties pane in the Elements panel

The Properties pane in the Elements tool is deprecated. Run console.dir($0) in the Console instead.

References

App shortcuts support in the Manifest pane

App shortcuts help users quickly start common or recommended tasks within a web app. The app shortcuts menu is shown only for Progressive Web Apps that are installed on the user's desktop or mobile device.

Download the Microsoft Edge preview channels

Cookies

Microsoft Edge Blocking Chrome

If you are on Windows or macOS, consider using the Microsoft Edge preview channels as your default development browser. The preview channels give you access to the latest DevTools features.

Getting in touch with Microsoft Edge Devtools team

Use the following options to discuss the new features and changes in the post, or anything else related to DevTools.

  • Send your feedback using the Send Feedback icon in DevTools.
  • Tweet at @EdgeDevTools.
  • Submit a suggestion to The Web We Want.
  • To file bugs about this article, use the following Feedback section.

Note

Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License.
The original page is found here and is authored by Kayce Basques (Technical Writer, Chrome DevTools & Lighthouse).

Does Microsoft Edge Block Google Chrome


This work is licensed under a Creative Commons Attribution 4.0 International License.