Screenshots

Description

postMessage-catcher shows the postMessage traffic of any page in a proper DevTools panel, instead of asking you to read a flooded console. What you get: • A live list of every message any frame of the page receives, with timestamp, origin, sender relationship, inferred type and size. • A detail pane with Overview, a collapsible Payload tree and the Raw snapshot. • Capture starts at document_start in every frame, including iframes, about:blank, srcdoc, data: and blob: frames, so handshakes and OAuth callbacks that fire during load are not missed. • Sender attribution you can trust: event.origin plus self / parent / child / other, even when the sender is cross-origin. • JSON string payloads are parsed automatically, with a Parsed / Text switch. That is how many widget and chat SDKs post their data. • History that survives reloads: the worker keeps a per-tab ring buffer, so you can open the panel after the bug happened. • Search, sender filters, keyboard navigation (Cmd/Ctrl+F, arrow keys) and JSON export. The active detail tab is kept while you move between messages. Built to do no harm: • The extension never wraps window.postMessage. Replacing that function would rewrite event.source and break pages that validate the sender, so capture is receive-only. • Page payloads are snapshotted with bounded budgets; cycles, Map, Set, BigInt, typed arrays and DOM nodes are represented, never thrown. • No network requests, no accounts, no telemetry, no remote code. Everything is processed and stored on your device. Good to know: • Works on regular http(s) pages. Chrome's own pages, extension pages, the Chrome Web Store and the PDF viewer cannot run content scripts. • targetOrigin is not shown: it is only visible on the sending side. • The sender's frameId is not knowable cross-origin; the panel shows origin and relationship instead. • MessagePort, BroadcastChannel and Worker traffic is not captured yet. • Frames that do not execute scripts (sandbox without allow-scripts) are invisible. Permissions: • storage — save your settings, per-tab recording flags and the captured history on your device. Open source under the MIT license. Source, issues and the privacy policy are linked below.