Loadtruck115

1. Edge For Linux Mint
2. Edge Chromium Pour Linux

Installation and Use Rights.For installation and use of the Software on any non-Windows platform, including but not limited to macOS and Linux, you may install and use one copy of the Software on any device running such non-Windows platform. When you launch Edge and Chromium side-by-side, you can even tell they are a part of the same family tree (Figure A). Figure A TechRepublic rendered with Edge (left) and Chromium (right). Oct 21, 2020 Edge Chromium is now available for Ubuntu, Fedora, and OpenSUSE but, ig you're rocking Arch Linux, here's how you can install Edge Chromium on Arch Linux. Apr 18, 2021 Microsoft has overhauled its Edge web browser which is now based on the open source Chromium browser. And, it’s finally available as beta on Linux. The new Microsoft Edge web browser on Linux.

When Microsoft announced plans to rebase its Edge browser on Chromium the chance of a dedicated Linux build went from pipe-dream to inevitability.

Chromium’s cross-platform codebase makes it the ideal foundation on which to build out a modern web browser. Three years since rumours first began swirling, Microsoft Edge for Linux is not only confirmed but it’s almost ready for testing.

Being the impatient sort we installed the Microsoft Edge Developer build on Ubuntu 20.10. This post will stop short of being a “review” per se (you’ll hear throughout this post: this is not a stable build) but I’ve included lots of screenshots and some general thoughts about how well the browser integrates with the default Ubuntu desktop.

You can test Chrome builds or Chromium builds. Chrome builds have the most infrastructure for analyzing crashes and reporting bugs. They also auto-update as new releases occur, which makes them a good choice for most uses.

Microsoft Edge for Linux Developer Build

Did I ever think I’d be writing a post about Microsoft’s flagship web browser being available for Linux? Heck no! And yet, here we are!

Many teeth have been gnashed over the point and purpose of a Microsoft-made web browser on a Linux platform. Some see Edge’s arrival as the latest bouquet in Microsoft’s blooming relationship with Linux and all things open source, but others? Well, they smell suspicion…

For their part Microsoft says its “motive” in bringing Edge to Linux is simply about making its technologies and services available to more users. Yes, even if they don’t run its Windows software (which is, after all, just one product/service in its portfolio).

Microsoft’s heavy presence in business, enterprise, and (increasingly) developer communities also plays a part. People who have to use Microsoft services at work get the chance to use the tech they’re familiar with and/or sync’d up with at home, on their Linux laptop, if they want.

But is there anything to interest casual Linux users too?

Edge is more than a Chrome clone; Microsoft had imbued Edge with custom touches and novel feature integrations. While many of these may sound superfluous to power-users they do, on other systems, round out the browser’s feature set.

Or to put it another way: Edge is a mass-market, all-user browser. It’s not aimed exclusively at any one audience, be that web developers, power users, or computer noobs.

So some of its “Added Value” may sound minor, trivial, or frivolous. Take Collections, for instance. This is essential just a souped-up bookmarking tool that lets you save content — not just web links — directly to the browser for future use.

You can create multiple collections in Edge, rename them, add notes to them, and export all of that data to other services (or copy of the links to the system clipboard).

On to integration. The Edge app launcher in the Ubuntu Dock does have a small right-click quicklist. This offers fast access to options to open a new window, a new incognito window, or quit the browser.

Sadly the Edge browser (like other Chromium browsers) does not use the system title/window bar by default. Edge draws its own window bar on Linux, with its own window control icons.

While the pale-grey bar Edge wears is not terribly distracting (unlike Vivaldi’s gaudy red window frame) some kind of GTK inheriting/colour detection (even if only an option) would be welcomed, I’m sure.

And Microsoft Account sync does not work in this build — but if you read this site regularly that will not be a surprise.

The good news is that many of Edge’s other features — yes, snarkypants, it does have some! — are present.

We’ve already touched on Collections, but there’s also an ‘immersive reader’ mode; integration with Bing; optional dark mode; web screenshot tool; and a variety of different New Tab page layouts (ranging from cluttered to calm);

You can install Chrome extensions on Edge easily. The first time you visit the Chrome Web Store using the browser it asks if you want to enable Chrome extension installs.

While I can’t vouch for the entirety of Chrome’s extension catalogue, all of the extensions I tried (yes, including the omg! ubuntu! one) worked as expected, as you can see above!

For an early version of Edge for Linux the browser feels fairly robust. It didn’t crash once during my test. Everything I asked of it, it did. From HD YouTube playback, to translating a Portuguese web page, to letting me play web games.

The app is fast to open and responsive in use. If Microsoft can maintain the friction-free feel it could win some new fans. Firefox isn’t slow, but a Chromium-based backend just feels so much faster in use (to me, anyhow).

Download Edge for Linux Dev Build

Want to try things out for yourself? We have a guide on how to install Edge on Ubuntu.

It’s not yet clear when Edge for Linux will go stable, but Microsoft has formally announced that it’s in developer preview. You can Linux builds on this Microsoft repo page.

If you jump on Edge for some early-bird testing just keep in mind that it is development software. It’s not finished. It’s not stable. Heck, it’s not even fully functional. Ergo, don’t get irate about any issues you encounter!

-->

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.

• 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.

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.

Edge For Linux Mint

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

Edge Chromium Pour Linux

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

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