You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked all your repos, but I couldn't identify the one containing the Windows browser code. Please point me to where I should open this issue. Thank you!
WINDOWS BROWSER - DOCK LOCATIONS OF DEVTOOLS NOT WORKING
I am evaluating the usage of DuckDuckGo. As I am a professional developer, I also need my PC browser to allow the usage of devtools.
Unfortunately, in the devtools of DuckDuckGo browser the dock location settings do not work: devtools appear in a separate window and there is no way to specify a different dock location and make it work. It always remains a separate window. This is a major no-no on my acceptance path.
I know that you're not developing the browser engine, but the dock location works in Chrome, so it must be something you can fix.
The text was updated successfully, but these errors were encountered:
Over 2 months later, I can confirm that this is still an issue. Just installed DuckDuckGo to test it out, and for me as well, this is a deal breaker. Hope it gets fixed soon. Or if there is a fix, someone can point to it.
I've checked all your repos, but I couldn't identify the one containing the Windows browser code. Please point me to where I should open this issue. Thank you!
WINDOWS BROWSER - DOCK LOCATIONS OF DEVTOOLS NOT WORKING
I am evaluating the usage of DuckDuckGo. As I am a professional developer, I also need my PC browser to allow the usage of devtools.
Unfortunately, in the devtools of DuckDuckGo browser the dock location settings do not work: devtools appear in a separate window and there is no way to specify a different dock location and make it work. It always remains a separate window. This is a major no-no on my acceptance path.
I know that you're not developing the browser engine, but the dock location works in Chrome, so it must be something you can fix.
The text was updated successfully, but these errors were encountered: