debugger-protocol-viewer
debugger-protocol-viewer copied to clipboard
DevTools Protocol API docs—its domains, methods, and events
Bumps [terser](https://github.com/terser/terser) from 4.6.10 to 4.8.1. Changelog Sourced from terser's changelog. v4.8.1 (backport) Security fix for RegExps that should not be evaluated (regexp DDOS) v4.8.0 Support for numeric separators (million...
Bumps [pug-code-gen](https://github.com/pugjs/pug) from 2.0.2 to 2.0.3. Commits eedf9a3 Don't ask escaping for boolean attributes at the beginning of attributes-list... 6f38adf Add in additional resources of 2 packages (#2945) d86ac52 new...
stepping back from #183 … I've always thought https://vanilla.aslushnikov.com/ is quite nice and competes well against this version. (I especially like that it needs [very little maintenance](https://github.com/aslushnikov/vanilla-protocol-viewer/commits/master)). The only reason...
lushnikov's protocol-viewer alternative has a sweet feature where you can see the references of a given type https://vanilla.aslushnikov.com/?Debugger.CallFrame  Super useful in figuring out what other methods use the same...
> **Chrome Version 95.0.4638.54** > > When I use devTools protocol "DOM.getFlattenedDocument", I got different results between the same site in two different network environments. The site has two layers...
One feature that got lost in the rewrite is the ability to permalink search result pages. This also enabled easy searching from within the Chrome address bar (by adding the...
Rather than the current Bash scripts, we should use a CI solution like GitHub Actions to deploy. Example action: https://github.com/marketplace/actions/deploy-to-github-pages
We are not showing methods/events that were moved to other domain in their old domain: https://github.com/ChromeDevTools/debugger-protocol-viewer/blob/ab43fc2e604ae82d250064d597341af46f542f0f/_includes/domain.html#L14 However, in search results we have links to both: new and the old domain....
It'd be really nice if the protocol viewer showed some sample messages ``` json { "callFrameId": "{\"ordinal\":0,\"injectedScriptId\":2}", "functionName": "module.exports.Router.extend.index", "location": { "scriptId": "34", "lineNumber": 26642, "columnNumber": 23 }, "scopeChain": [...
I often find myself revisiting same sections of documentation. I'd be great to keep info about previous searches and feature visited sections in the future searches.