Auto-open DevTools for popups is a feature in den Dev tools of Chrome.
I've checked this functionality in dev tools settings, but it just won't work.
Tried it with latest Chrome build (52), Canary and Chromium, same problem.
I've restarted Chrome, PC, tried it with opened Dev Tools and without.
Only thing which is working is to add the "--auto-open-devtools-for-tabs" flag in the Chrome startup options.
Are there any known bugs about this? It is a little it annoying to add/remove the flag everytime.
Or any other ideas about this?
Thanks
Bene
Related
I have a chrome browser open. I press f12 and nothing happens. I click the three dots at the top right, click More Tools, click Developer Tools, and nothing happens. The Developer Tools options is not grayed out. There is no icon in the task bar so this isn't a "hidden window" issue. I've restarted Chrome. I've rebooted and I've uninstalled/reinstalled Chrome. I'm on Chrome version Version 89.0.4389.82 (Official Build) (64-bit) and Windows 10 Version 1909 (OS Build 18363.1440). What steps can I take to resolve this.
UPDATE: Using chrome task manager, I do see that the dev tools process is being kicked off and running, it's just not visible in any way.
UPDATE 2: If I run in incognito mode, devtools works. I have already disabled all extensions and cleared all site data (cookies and files). Still nothing for devtools in non-incognito chrome.
I found there is no hex viewer in my Chrome's WebSocket dev tools, as in picture 2, unlike picture 1 on my colleague's computer.
I didn't find corresponding view settings. I tried to reboot my computer and reinstall Chrome, even the beta version, still not work.
Thanks to someone who would help me out!
OS version: macOS Catalina 10.15.7, Chrome version: 87.0.4280.88
picture1 normal view
picture2 no encoding settings
This appears to be a bug in Chrome 87. I suspect that your colleague is using a different Chrome version.
See https://bugs.chromium.org/p/chromium/issues/detail?id=1151164#c7, which claims that the bug was fixed in Chrome 89.0.4348.0. The solution appears to be one of:
Switch to the Chrome Beta channel
Use a debug extension for Chrome such as WebSocket Frame Inspector as suggested here.
See also these related SO questions:
How can I change the binary message display format in the Chrome/Edge debugger?
Chrome DevTools. The encoding switch bar of the websocket frame viewer disappeared
When i try to run example code from: https://webrtc.github.io/samples/src/content/capture/video-pc/
on Google chrome Version 54.0.2840.90 (64-bit) on Linux Mint, it's not working. Firefox works fine.
What's the problem?
I noticed the same issue and it seems like you have to enable "Experimental Web Platform features" in Chrome in order for the demo to work.
Go to chrome://flags
search for "Experimental Web Platform features"
Enable and relaunch.
Unfortunately it still doesn't work properly, at least when loading the page initially. If I drag the player location though, it seems to work.
I'm having an issue with getting Chrome's Developer Tools to work on my machine.
I've tried both Chrome Version 37.0.2026.0 canary and Version 35.0.1916.114 m and both have slightly different problems - I'm using Windows 8.1.
In the standard installation of Chrome, the Developer Tools options are greyed out. I've searched this everywhere and there is a Google post saying to enable it in your registry settings. When I go into my registry, there is nothing relating to Google in the path they've specified - [http://www.chromium.org/administrators/policy-list-3#DeveloperToolsDisabled][1]
In the Canary version of Chrome, the Developer Tools options appear and are not greyed out or anything, but absolutely nothing appears when I click it (no window, no error, nothing).
Anyone have any ideas? I've tried restarting the machine, clearing my cache, reinstalling Chrome but no solution..
I'll keep looking for a solution and post it if I find anything!
Thanks in advanced.
Ohhhh! I went through my Chrome settings again and noticed that Javascript was being "enforced by my administrator"
I figured out what it was (so stupid): We use Google Apps where I work and it's been disabled in the Admin Console. You definitely pointed me in the right direction though!
I've just installed Google Canary on my Mac. I want to have a play with the Experiments in the google developer tools. But I can't for the life of me find where/how to enable them.
I specifically want to look at using/editing SASS in the browser.
Thanks
dave
Found it
In chrome go to chrome://flags and enable it there.
Go to chrome://flags.
Find Developer Tools Experiments.
Enable it.
Click Relaunch Now to relaunch Chrome.
In the DevTools settings, there's now a new Experiments tab.
Cheers