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
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.
In this release announcement about the Chrome debugger capabilities https://developers.google.com/web/updates/2019/03/devtools, Kayce Basques writes:
Use the dropdown menu at the bottom of the viewer to convert the message into Base64 or UTF-8. Click Copy to clipboard Copy to clipboard to copy the binary message to your clipboard.
Figure 8 shows a bar with the words "Hex Viewer":
(source: google.com)
In Chrome Version 88.0.4324.96 (Official Build) (x86_64) and Edge Version 88.0.705.53 (Official build) (64-bit), on MacOS, this bar doesn't seem to exist:
Chrome:
Edge:
Is there a way to view binary websocket messages in a format other than base64 in the latest Chrome/Edge network debuggers, or has this functionality been removed entirely?
I've discovered this chromium bug that appears to be fixed in Chrome 89.0.4348.0.
https://bugs.chromium.org/p/chromium/issues/detail?id=1151164#c7
This is also answered in Chrome DevTools. The encoding switch bar of the websocket frame viewer disappeared
I'm confused I don't know if the latest update of chrome AKA version 73 just integrated this attribute on purpose but I'm getting a strange attribute that I did not added into my web pages and i'm wondering what this means in chrome?
CHROME BROWSER
EDGE BROWSER
Should I be concern with this? It's only showing on Chrome.
There is another Chrome and Firefox plugin that does same, sadly, but probably one of best VPN tools Urban VPN Browser Extension. The solution is same, just deactivate. Btw, those guys have other extensions, haven't tested others.
Just uninstall any type of VPN that you installed in you browser and afterwards bis_skin_checked="1" will removed automatically.
The attribute is added just because of one of an extension of the Chrome Browser you have installed in your Chrome Browser. I also got this attribute added to my HTML when checking in the console. Then I replicate this by deactivating extensions one by one and found it's adding from Hover Over extension.
This problem has happened to me recently. I installed the Urban VPN plugin and after that, I faced this issue. But uninstalling the plugin, the problem is solved.
I've got the SpeakIt! [Version 0.3.20] extension installed for Chrome [Version 74.0.3729.131 (Official Build) (64-bit)] on Windows 10, and I am seeing the same bis_skin_checked="1" when it's enabled. When I disable the SpeakIt! extension, the bis_skin_checked="1" goes away.
This thing append from different Chrome/Mozilla extension.
Disable recent extensions to see the changes(bis_skin_checked="1" goes away
).
Hi I was using selenium chrome drivers as interactive service to open some websites. It was working fine. Suddenly found that the session is not loading correctly and showing black page. Found following error:
chrome automation extension has crashed. click this balloon to reload the extension
Found that with chrome browser version was updated to v51 and selenium-chromedriver 2.21 is compatible with v50.
Downgraded chrome browser to v50. Now it is working fine.
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!