like we have in Google Chrome and with Firebug in Firefox.

When I create a new custom profile in the emulation settings, allow to save it.

Enable F12 to open in Continuum for mobile.

When you do a console.log("hello"), then the text "hello" will be outputted to the console, and then there will also be outputted a "source-link" below that line which can take you to the sourcecode and line of where that console.log was executed.

So if you do 5 console.log, then there will be 10 lines because of the source-link

Can you put the source-link to the right or top-right corner on every log, because that would save many lines and be more readable.

That is was Chrome does.

Grouping tags under specific handlers will make navigation easier and avoid all unnecessary work searching for the handler that trigger a specific event

We need an option to export current debugging session to file so we can debug it locally...

E.g. Export currently loaded html page to file,
Export currently loaded DOM to file,
with loaded CSS and Javascript,
Inc current session cookies for offline use

So we can debug issues locally offline and also supply to third parties so they can reproduce bugs which exist on production and are hard to replicate

Please allow to dock the dev tools to the side of the window. Also, allow for a separate tab row for and pinned tabs for JavaScript files (like in Visual Studio)

This small thing would go a long way for many developers on Edge!

Thanks!

I want to simply add border-bottom as a CSS attribute to test an issue i have, however it does not allow me to do that.

( border-bootm, border-left, border-right, and border-top ) @ add to list...

I have managed to do it by typing: border-bottom and then clicking out of it.

However the option in the drop down should contain this attribute.

The "always record developer console messages" setting in Internet Options is respected by IE but not Edge. This is the #1 reason why I do not use Edge for developing and testing my app. I don't always remember to hit F12 when testing and having all of my logs get lost because of this is a huge detractor.

If dev tools are undocked, it seems impossible to debug web apps which use Fullscreen API on a single display.

* Launch app
* Open dev tools
* Take appropriate user action to enter fullscreen
* Switch to dev tools window

Expected: app remains in fullscreen.
Actual: app drops out of fullscreen.

The only way I've found to effectively debug fullscreen web apps with Edge is by using multiple displays - dev tools on one, app on another.

Docking (vertical or horizontal) should be supported in this scenario as well.

Testing Edge on localhost can sometimes be a pain. Especially when we load resources from CDNs (like our own). In a mixed localhost / cdn Environment one will always see "This Internet Explorer instance does not have privateNetworkClientServer capabilities", which is a) misleading, since i'm using edge, not IE and is frustrating, since there is no internal Workaround. Fiddler allows me to remap mylocalhost to localhost, which solves the Problem, but I - as a developer - would like to just use it for development, as I do with all my other Browsers.

Both Chrome and Firefox allow developers to manage cookies.Our QA and QE need some cookie editing tools that are more accessible than the console.

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.

allow easily design responsive page using media query by emulating different resolutions (like the way Chrome does - Device emulation)

have console window always visible at the bottom just like the way in Chrome

Every time I open the Dev tools the browser slows a lot and crash often especially with heavy sites. This do not happen with Chrome.
Resizing the view also is incredibly slow and stuck my workstation.

This makes it almost impossible to use even if I would gladly use it instead of the Chrome one

Steps to reproduce the problem:
1. open the devtools network panel
2. upload a file using html file upload

What is the expected behavior?
The size of the upload to be visible for the individual network request and also counted in the status bar transfer summary

I have currently built a browser extension for Chrome that allows me to add a new pane to the DevTools that has its own UI and can communicate with the current tab with a background page for the extensions.

I would like to be able to write the same extension for Edge. That allowed me to do the same.