Edge Microsoft Chromium

-->

Microsoft has adopted the Chromium open source project in the development of Microsoft Edge on the desktop to create better web compatibility. This new Microsoft Edge runs on the same Chromium web engine as the Google Chrome browser, offering you best in class web compatibility and performance. Microsoft launched Edge based on Google's Chromium open source project for Windows 7, Windows 10, and macOS. This is Edge 79 stable. Chromium Edge, a new era Microsoft shocked everyone when it announced that the next version of its Edge browser would run on Google's Chromium, the open-source engine behind Chrome. By switching to.

An extension is a small program that you (a developer) use to add or modify features for Microsoft Edge (Chromium). An extension is intended to improve a user's day-to-day browsing experience. It provides niche functionality that is important to a target audience.

You may create an extension if you have an idea or product that is based upon either of the following conditions.

• A specific web browser.
• Improvements to features of specific webpages.

Examples of companion experiences include ad blockers and password managers.

An extension is structured similar to a regular web app. At a minimum, it should include the following features.

• An app manifest JSON file that contains basic platform information.
• A JavaScript file that define functionality.
• HTML and CSS files that define the user interface.

To work directly with part of the browser, such as a window or tab, you must send API requests and often reference the browser by name.

Basic guidance

Some of the most popular browsers to build extensions for include Safari, Firefox, Chrome, Opera, Brave, and Microsoft Edge. Great places to begin your extension development tutorials and documentation research are sites hosted by the browser organizations. The following table isn't definitive, and may be used as a starting point.

Microsoft Edge Chromium Beta Download

Important

Many of the tutorials of the sites use browser-specific APIs that may not match the browser for which you develop. In most cases, a Chromium extension works as-is in different Chromium browsers and the APIs work as expected. Only some less common APIs may be strictly browser-specific. For links to the tutorials, navigate to See also.

Why Chromium?

If your goal is to publish your extension in the extensions store for each browser, it must be modified for each version to target and run in each distinct browser environment. For example, Safari extensions may use both web and native code to communicate with counterpart native applications. The last four browsers in the previous table use the same code package, and minimizes the requirement to maintain parallel versions. These browsers are based on the Chromium open-source project.

Create a Chromium extension to write the least amount of code. It also targets the maximum number of extension stores and ultimately the maximum number of users who find and acquire your extension.

The following content focuses mostly on Chromium extensions.

Browser compatibility and extension testing

Occasionally, API parity doesn't exist between Chromium browsers. For example, there are differences in the identity and payment APIs. To ensure your extension meets customer expectations, review API status through the following official browser docs.

The APIs you require define the changes you must make to address the differences between each browser. It may mean that you must create slightly different code packages with small differences for each store.

To test your extension in different environments before you submit it to a browser store, sideload it into your browser while you develop it.

Publish your extension to browser stores

You may submit and seek browser extensions in the following browser stores.

Some stores allow you to download listed extensions from other browsers. However, cross-browser access is not guaranteed by browser stores. To ensure your users find your extension in different browsers, you should maintain a listing on each browser extension store.

Users may need to install your extension in different browsers. In this scenario, you may migrate existing Chromium extensions from one browser to another.

Migrate an existing extension to Microsoft Edge

If you've already developed an extension for another Chromium browser, you may submit it to the Microsoft Edge Add-ons store. You don't need to rewrite your extension, and must verify it works in Microsoft Edge. When you migrate an existing Chromium extension to other Chromium browsers, ensure the same APIs or alternatives are available for your target browser.

For more information on porting your Chrome extension to Microsoft Edge, navigate to Port Chrome extensions to Microsoft Edge (Chromium). After you port your extension to the target browser, the next step is to publish it.

Publish to the Microsoft Edge add-ons website

To start publishing your extension to Microsoft Edge, you must register for a developer account with an MSA email account to submit your extension listing to the store. An MSA email account includes @outlook.com, @live.com, and so on. When you choose an email address to register, consider if you must transfer or share ownership of the extension with others in your organization. After registration is complete, you may create a new extension submission to the store.

To submit your extension to the store, ensure you provide the following items.

• An archive (.zip) file that contains your code files.
• All required visual assets, which include a logo and small promotional tile.
• Optional promotional media, such as screenshots, promotional tiles, and a video URL.
• Information that describes your extension such as the name, short description, and a privacy policy link.

Note

Different stores may have different submission requirements. The above list summarizes the requirements to publish an extension for Microsoft Edge.

After you've successfully submitted your extension, your extension undergoes a review process and either passes or fails the certification process. Owners are notified of the outcome and given next steps as required. If you submit an extension update to the store, a new review process is started.

See also

When you install Microsoft Edge, you get a browser. Also, you get a powerful way to inspect, debug, and even create web projects. The Developer Tools shipped with the browser are based on the tools in the Chromium open-source project, so you may already be familiar with the tools. To keep descriptions shorter in this article, the Microsoft Edge Developer Tools are now referred to as DevTools .

Use DevTools to review and learn more about the following development tasks.

• Inspect and change the current webpage live in the browser.
• Emulate how your product behaves on different devices and simulate a mobile environment complete with different network conditions.
• Inspect, tweak, and change the styles of elements in the webpage using live tools with a visual interface.
• Debug your JavaScript using breakpoint debugging and with the live console.
• Find accessibility, performance, compatibility, and security issues in your products and learn how to use DevTools to fix each.
• Inspect the network traffic and review the location of the problems.
• Inspect where the browser stored content in various formats.
• Evaluate the performance of your product to find memory problems and rendering issues.
• Use a development environment to sync changes in DevTools with the file system and override files from the web.

And a lot more. It all starts when you open DevTools and customize each tool to your needs.

Open the DevTools

To open and explore the DevTools, use one any of the following actions.

Edge Microsoft Chromium

• Hover on any element on the webpage, open the contextual menu (right-click), and then choose Inspect. This action opens the Elements tool.
• Select F12.
• Select Ctrl+Shift+I on Windows/Linux or Command+Option+I on macOS.

Microsoft Edge Chromium Offline Installer

There are two main ways to interact with the DevTools.

• Use the mouse
• Keyboard shortcuts. Keyboard shortcuts provide a quick way to access functionality and are needed for accessibility. The Microsoft Edge DevTools team works hard to make all the tools available using the keyboard and assistive technologies such as screen readers. For more information about how to open the different features in the DevTools, navigate to Microsoft Edge DevTools keyboard shortcuts.

Dock the DevTools in your browser

When you open the DevTools, it docks to the left of your browser. To change the docked location of the DevTools, complete the following actions.

1. Choose the Customize And Control DevTools (...) button.
2. To the right of Placement of the DevTools relative to the page (Dock side), choose a Dock side option.

For more information, navigate to Change Microsoft Edge DevTools placement (Undock, Dock To Bottom, Dock To Left).

In Dock side, choose any of the following layout options.

• Undock into separate window. Helps you work with several monitors or if you need to work on a full screen app.
• Dock to left or Dock to right. Helps you keep the DevTools side by side with your web product, and is excellent when you emulate mobile devices. The Dock to left and Dock to right options work best with high-resolution displays. For more information about emulation devices, navigate to Emulate mobile devices in Microsoft Edge DevTools.
• Dock to bottom. Helps you when you do not have enough horizontal display space, or you want to debug long text in the DOM or Console.

Learn about the core tools

DevTools give you an amazing amount of power to inspect, debug, and change the web product currently displayed in the browser. Most of the tools display the changes live. Live updates make the tools incredibly useful to refine the appearance and navigation or functionality of a web project without the need to refresh or build it. The DevTools also allow you to change web-based third-party products on your computer.

DevTools grew over a period of several years. You may assume that DevTools are difficult to learn when you first open any of tools. The following text quickly introduces the different parts. The main toolbar offers you a few sections and the sections are ordered from left to right.

• The Inspect Tool allows you to choose an element on the current webpage. After you activate it, you may move your mouse over different parts of the webpage to get detailed information about the element and a color overlay to display dimensions, padding, and margin.

• The Device Emulation tool displays the current web product in an emulated device mode. The Device Emulation tool allows you to run and test how your product reacts when you resize the browser. It also gives you an estimation of the layout and behavior on a mobile device.

• The Tools tab group is a group of tabs that represent different tools that are used in different scenarios. You may customize each of the tools and each tool may change based on the context. To open a dropdown menu of more tools, choose the More tabs (>>) button. Each of the tools is introduced later in the following section.

• Next to the Tools tab group are optional error and issues shortcuts. The shortcuts display when JavaScript errors or issues occur on the current webpage. The Open Console to view # errors, # warnings (JavaScript Errors) button displays a red circle with an X followed by the number of JavaScript errors. To open the Console and learn about the error, choose the JavaScript Errors button. The Open Issues to view # issues (Issues) button is a blue message icon followed by the number of issues. To open the Issues tool, choose Issues button.

• The Settings button displays a gear icon. To open DevTools Settings webpage, choose the Settings button. The Settings webpage displays a menu to change Preferences, turn on Experiments, and much more.

• The Send Feedback button displays torso with a chat bubble next to it. To open the Send Feedback dialog, choose the Send Feedback button. The Send Feedback dialog allows you to enter information to describe what happened and automatically includes a screenshot. Use it to connect with the DevTools team to report problems, issues, or suggest ideas.

• The Customize and control Devtools (...) button opens a dropdown menu. It allows you to define where to dock the DevTools, search, open different tools, and much more.

In the Tools tab group, you may open the different tools that are available in the DevTools. The following list describes the most commonly used tools in the DevTools.

• Welcome. Includes information about the new features of DevTools, how to contact the team, and provides information about certain features.
• Elements. Allows you to edit or inspect HTML and CSS. You may edit both in the tool and display the changes live in the browser.
• Console. Allows you to display and filter log messages. Log messages are automated logs of the browser like network requests and developer-generated logs. You may also run JavaScript directly in the Console in the context of the current window or frame.
• Sources. A code editor and JavaScript debugger. You may edit projects, maintain snippets, and debug your current project.
• Network. Allows you to monitor and inspect requests or responses from the network and browser cache. You may filter requests and responses to fit your needs and simulate different network conditions. Other specialized tools are also available, such as Performance, Memory, Application, Security, and Audits.

Power tip: Use the command menu

The DevTools provides lots of features and functionality to use with your web product. Access the different parts of the DevTools in many ways, but the fastest way to access the features you need is to use the command menu. For more information, navigate to Run commands with the Microsoft Edge DevTools Command menu. To open the command menu, complete one of the following actions.

• Select Control+Shift+P (Windows, Linux) or Command+Shift+P (macOS).
• Choose Customize And Control DevTools (...), and then choose Run Command.

The command menu allows you to type commands to display, hide, or run features in the DevTools. With the command menu open, enter the word changes, and then choose Drawer Show Changes. The Changes tool opens which is useful when you edit CSS, but is difficult to find in the DevTools UI.

Customize the DevTools

DevTools are customizable to meet your needs or the way you work. To change settings, complete one of the following actions.

• Choose Settings (the gear icon on the top right)
• Select F1 or ?.

In the Preferences section, you may change several parts of the DevTools. For example, you may use the Match the browser language setting to use the same language in the DevTools that is use in your browser. For another example, use the Theme setting to change the theme of the DevTools.

You may also change the settings of advanced features including the following features.

• Workspaces.

• Filter library code with the Ignore List.

• Define the Devices you want to include in the device simulation and test mode. For more information, navigate to Emulate mobile devices in Microsoft Edge DevTools.

• Choose a network Throttling profile.

• Define simulated Locations.

• Customize keyboard shortcuts. To use the same shortcuts in the DevTools as Visual Studio Code, complete the following actions.

  1. Choose Match shortcuts from preset.
  2. Choose Visual Studio Code.

Try experimental features

The DevTools team provides new features as experiments in the DevTools. To get the full list of experiments, navigate to the DevTools Settings, and then choose Experiments. You may turn each of the experiments on or off. Help decide which one of the experiments is valuable to you. For more information on the experiments, navigate to Experimental features.

Getting in touch with the Microsoft Edge DevTools team

Update Microsoft Edge

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 or select Alt+Shift+I (Windows, Linux) or Option+Shift+I (macOS) in DevTools.
• Tweet at @EdgeDevTools.
• Submit a suggestion to The Web We Want.
• To file bugs about this article, use the following Feedback section.

If you want to preview the latest features coming to the DevTools, download Microsoft Edge Canary, which builds nightly.

See also