How can I test the behavior of a Chrome extension when prerender/prefetch occures? Specifically, I would like to see tabs.onReplaced and webNavigation.onTabReplced fired.
I have checked the chrome://net-internals/#prerender page, the prerender is enabled, but I never see it in use.
I use the latest version of Chrome (Version 63.0.3239.84).
Related
This issue has been plaguing me for about a week now. On the latest Chrome version, I'm unable to open a WebSocket request via DevTools to see individual frames. This is happening on all websites.
I have no filter added anywhere I can see, so the invalid regex issue that I'm seeing in the Devtools' devtools window is a mystery.
I'm on Chrome Version 106.0.5249.103 (Official Build) (arm64), on OSX, and haven't seen this problem before.
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
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
in my chrome browser when i see
chrome://chrome/
it shows the chrome browser is up to date , but when i open console in developer tools i cant able to use the latest chrome (36) javascript interpreter features like
Object.observe();
How to update this ?
Are you using Chrome beta channel? Object.observe() works in Chrome beta (36), you can also check chrome://version, mine is 36.0.1985.49
We are trying to run some automated tests (coded ui based) on our mobile application via Chrome browser.
In order to make the tests available to run, we must set the browser to work as 'emulate touch events'.
The thing is that as part of our test flow, a new chrome browser is being launched on each test but the definition is gone.
I already check this one, but it doesn't work:
How to Always Emulate Touch Events in Chrome Dev Tools?
Any other suggestions?
Thanks,
Yair
I believe that the dev tools window must be opened for the overrides to kick in, have you tried that?