I feel the DOM Inspector font as being too large when I'm debugging web pages having a number of windows (incl. web page and F12 window) spread across the screen. In the restricted space available for the F12 window (particularly when it's docked to the bottom of the browser window) I can hardly get to see three lines of HTML.

So, please add a Font Settings option to F12DT so I can choose a smaller font size for DOM inspector and other F12DT panels, resp.

And please add a Boolean option for disabling word wrap in DOM inspector.

When working with links that open in a new tab, I have to start the dev tools after the site starts loading for that tab. If I have dev tools open in the previous tab then start dev tools in the linked tab so I get the initialization. Starting the dev tools after the tab starts means the tools aren't running when that site loads. Add it as an option in the about:flags page.

'ytcfg' is undefined on YOUTUBE. report it so YOUTUBE can fix it
A window opened saying a bug was found on this page, it asked if I would like to debug it, I DO NOT OWN YOUTUBE, YOUTUBE NEEDS TO BE MADE AWARE THIS BUG IS ON THEIR WEBSITE SO THEY CAN FIX IT, WHY DOES THE DEBUGGER ASK ME TO FIX IT, AND NOT SEND A REPORT TO YOUTUBE AS IT SHOULD

This feature would extend the emulation tool to enable throttling of the CPU to emulate situations where the page is running on a low CPU device. The emulation is not perfect (e.g. it wouldn't emulate diff instruction sets) but would help in giving a more real world experience for lower powered devices (desktop and phone).

Allow to save edits made to local CSS files in the dev tools.

This feature would use some rule checking against the acc tree and properties to point out potential issues. For example when an img is missing a name (say because of a missing alt attribute) or a labelledby is pointing to an invalid node etc.

This feature would articulate how the various accessibility properties in the accessibility panel are calculated. For example where the name value comes from.

To locate bugs, it would be great to be able to disable JavaScript via Developer Tools. A button in the Debugger tool bar, for instance.

As the title says, being able to activate the element highlighting after interacted with the page would be very useful

Currently in the debugger, after the source maps are loaded, the combined javascript files are removed from the source tree which makes following up production stack traces challenging.

Firefox has a similiar problem https://bugzilla.mozilla.org/show_bug.cgi?id=1301331

Firefox and all webkit-based browser have a 'copy' function injected into the console, which can be used to copy the content of any variable currently in the console to the clipboard. I recently discovered this in Opera, and it's become a very handy functionality. Please add this to Edge too.

Nowadays many of us test on the phone to, so please let us get access to f12 on mobile to. Would be so nice to inspect elements on the mobile to!!

If Edge cannot find source files from map.js, the debugger becomes worthless. It does not allow me to easily Show the js files nor does it ask me, where to look for the original source files in the file System.
Chrome solves this a Little bit better by allowing me to define a Workspace. You should enable something similar.

When using the Network tab in Edge Developer Tools, it would be cool to have Edit and Resend request option (something similar to what Firefox offers).

The find text box is aligned in the top right corner next to the CSS, it's un-intuitive and should be nearer to the DOM inspector window

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.

Often time customers want to see how often a particular thing occurred in the timeline. Like document.createElement(). Manually counting these on large web pages or highly graphical ones can be nearly impossible.

What would be useful in order to better support IE and Edge and thus reduce the escalations to EE's would be the ability to export to a CSV or excel so that we could actually run count() functions on particular elements or occurrences.

Need a way to detect Enterprise Mode from client side code

This should be pretty straight forward, but I would really like to be able to copy text from the F-12 developer tools when working with memory snapshots.

It makes it easier to paste it later when I hit control-f in the debugger later.

Right now I can take screen shots, and then I end up having to type out really long class names, or IDs which I could misspell.

The events tab should show mutation observers along with their configuration just like other events.