Support websocket inspection in the devtools
See original GitHub issueDescription
The devtools does not have a websocket inspector. As a dev, I’d like to inspect active websockets like I can with Chrome.
Steps to Reproduce
- Open the inspector
- Go to
Network
- There is no option to view websocket connections
Actual result:
Brave:
![image](https://user-images.githubusercontent.com/855434/206819502-58965ef2-2af3-45a0-b8a0-c93a3202ed30.png)
Expected result:
Chrome:
![image](https://user-images.githubusercontent.com/855434/206819491-a9409a90-4ca8-4230-b5fb-bbaf7b3c80de.png)
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Brave | 1.45.133 Chromium: 107.0.5304.141 (Official Build) (x86_64)
-- | --
Revision | cddb1ab381a982f400a57e15e14080e1aaaca4b8-refs/branch-heads/5304_105@{#3}
OS | macOS Version 13.0.1 (Build 22A400)
JavaScript | V8 10.7.193.22
User Agent | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
Command Line | /Applications/Brave Browser.app/Contents/MacOS/Brave Browser --disable-domain-reliability --enable-dom-distiller --component-updater=url-source=https://go-updater.brave.com/extensions --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --flag-switches-begin --flag-switches-end
Executable Path | /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path | /Users/theo/Library/Application Support/BraveSoftware/Brave-Browser/Default
Linker | lld
Active Variations | AdRewardsStudy:NextPaymentDayAdvertiserSplitTestStudy:GroupAAllowCertainClientHintsStudy:EnabledBraveAdblockCookieListOptInReleaseStudy:EnabledBraveAds.AdServingStudy:DefaultAdNotificationsPerHour=10/MaximumAdNotificationsPerDay=100/MaximumInlineContentAdsPerHour=12/MaximumInlineContentAdsPerDay=60/AdServingVersion=1BraveAds.FrequencyCappingStudy:ExcludeAdIfWithinTimeWindow=0hBraveAds.UserActivityStudy:Triggers=NTPSI/TimeWindow=15m/Threshold=0.0/IdleTimeThreshold=5sBraveDebounceStudy:EnabledBraveRewardsWebUiPanelStudy:EnabledBraveScreenFingerprintingBlockerStudy:DefaultConversionsStudy:NewDefaultPatternDefault1pBlockingStudy:DisabledDisableReduceLanguage:EnabledEphemeralStorageStudy:EnabledFirstPartyEphemeralDomainBlockStudy:EnabledForceDisableBlinkFeatures:EnabledMacCoreLocationBackendStudy:EnabledPartitionBlinkMemoryCacheStudy:EnabledPartitionConnectionsByNetworkIsolationKeyStudy:EnabledPermissionLifetimeReleaseStudy:EnabledSpeedreaderReleaseStudy:Enabled
Issue Analytics
- State:
- Created 9 months ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
What's New In DevTools (Chrome 74)
Click the Name of a WebSocket connection to inspect it. Click the Messages tab. Click one of the Binary Message entries to inspect...
Read more >How do you inspect websocket traffic with Chrome Developer ...
I'm trying to inspect websocket traffic using Chrome Developer Tools. From my research it seems you should be able to see it using...
Read more >Inspecting WebSocket Traffic with Chrome Developer Tools
Inspecting WebSocket Traffic with Chrome Developer Tools · Be sure that your Chrome version is 58+. · Navigate to the Echo demo, hosted...
Read more >Inspecting WebSocket Traffic - Springer Link
Chrome's Network tab provides unique insight not only into the WebSocket handshake but also allows you to easily inspect the WebSocket frames.
Read more >Socket.io inspection techniques to simplify realtime app ...
Inspect messages with the Chrome developer tools ... it has fairly rich support for inspecting WebSocket connection traffic.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There’s already a separate issue for an incorrect button color: https://github.com/brave/brave-browser/issues/27437
@goodov should we re-open since the display state is wrong?