Highlights
🐛 Chrome-required fields the bridge was omitting
Two events the bridge emits were missing parameters Chrome's protocol requires, which a strict client can depend on: Debugger.scriptParsed now carries a hash and executionContextId, and Page.frameNavigated carries its type. Both are verified against node --inspect. A new schema check validates every emitted event, so a missing field now fails a test instead of a client.
🐛 The landing page no longer floods the log
The landing page polls GET /api/targets about once a second; those access lines are now logged at debug, so the default output stays clean. Run with -v to see them again.
✅ Golden editor-flow regression tests
Real WebStorm (JSContext) and Safari-page debugging sessions now replay through the bridge offline in CI and assert stepping advances with the paused/resumed alternation editors need. A future change that breaks stepping or an emitted event's shape fails in CI instead of in someone's editor.
What's Changed
- ada8174 cdp: Add a page-path golden flow and check emitted events in the golden tests (#1932) (@doronz88)
- f73d79c cdp: Validate emitted events against Chrome's schema and fill the fields it flags (#1932) (@doronz88)
- 28cd591 cdp: Add golden editor-flow regression tests (#1931) (@doronz88)
- fcdfc50 cdp: Log GET access lines at debug so the landing-page polling stops flooding output (#1930) (@doronz88)
Full Changelog: v11.10.1...v11.10.2