Microsoft Edge on windows does not include the version of the browser but only the version of layout engine:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763

The version should be 44.17763.1.0, since 18.17763 is the version of layout engine

I suggest something like:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/44.17763.1.0 (EdgeHTML 18.17763)

The old version of this tool showed me the actual payload string but now shows the key/val pairs broken down and sorted alphabetically. This isn't useful for me any more. Please include an option to show the ACTUAL payload string as is built and sent.

This feature would show the current size of the Page (innerHeight and innerWidth) in a small label drawn in F12 as Edge is resized. The dimensions in the label would update as the Edge window is resized.

The F12 window gets closed when opening a website or during auth redirect, which makes it impossible to debug auth failures and JS errors happening during website initialization.

This feature would enable the emulation of different network connections such as 3G, 4G etc... changing network throughput, latency and packet loss to match typical conditions for that type of network.

Proposed Design
- Impacts just the page being debugged
- Dropdown on emulation tool to select from the different connection options (exact list tbd)
- Fits in with the persistence of the rest of the emulation settings

Add optional Visual Studio-like Dark theme. Eyes work harder going from VS Dark to F12 Tools light hundred of times a day. Less fatigue, more productivity.

As a SharePoint and web developer, I often have to create and troubleshoot HTTP REST calls. I would like to manipulate the querystring, headers and body as well as use different HTTP methods (GET, POST, PUT, DELETE, etc.) and see the results.

There is currently, as far as I can see, no way to view the layout of printed document and the CSS styles that will be applied when printed. In Chrome you can choose to emulate @media print mode and inspect the document.

I am trying to debug why the text of a document printed from Chrome and IE11 has such wildly different text sizes but I cannot trace the font-size styles in IE to compare it to the font-size in Chrome.

It would be nice to see the indexedDB database in dev-tools.
Think about:
* Version
* ObjectStores
* Data in objectstores
* Indexes for objectstores

This feature allows the network tool to display websocket data.

Proposed Design
-Mark HTTP requests that are upgraded to WS in the summary grid
-Add a WS Frames tab in the details view to display the data
-Frames panel displays plains text data and calls out binary opcodes and origin of the data

Need a mechanism to turn around a photograph in yahoo mail.

Enable Migration of Password from Firefox/Chrome or at least via a XML file into Edge. Chrome/Firefox lets you export the password to a XML File and this can be used to import the same into Edge. This is the main thing that is keeping me away from using Edge.

It would be awesome (and expected) to be able to interact with Edge using PowerShell. Automating the importing/exporting of favorites for example would be great.

Take a look at the Chrome console: You can switch the current context from the main thread to every web worker which got created. This is extremely useful for debugging workers.

it is kind of annoying to get outputs like "test [Object object]".
this is implemented in Chrome, Safari & FF for a long time already.

This feature would mirror what Chrome DevTools has, where non-enumerable members of evaluated objects are displayed in the console and Watches / Locals. To signify they are non-enumerable, the member names are greyed out.