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,
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 replicate3 votes
This small thing would go a long way for many developers on Edge!
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.6 votes
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.28 votes
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.7 votes
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.127 votes
have console window always visible at the bottom just like the way in Chrome4 votes
allow easily design responsive page using media query by emulating different resolutions (like the way Chrome does - Device emulation)6 votes
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.16 votes
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 one126 votes
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 summary1 vote
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.22 votes
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.70 votes
Currently when I open and close developer tools its often puts edge into an apparent "not responding" state for a few seconds. This makes the platform seem very low quality despite the fact edge in general is great.
This also has the effect of if you are paused in a debugging session on a breakpoint you cannot just press F5 to refresh the page you have to stop the debugger since the UI is locked up... Chrome/Firefox/Safari doesn't do this.2 votes
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.5 votes
Chrome and Firefox support styling the console text.
I use the feature a lot and I would really appreciate to have it in Edge.22 votes
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.1 vote
'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 SHOULD1 vote
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).8 votes
Allow to save edits made to local CSS files in the dev tools.5 votes
- Don't see your idea?