[Protocol Monitor] Fix behavior for optional object parameters Screencast: https://screencast.googleplex.com/cast/NTQzMDU4MzQ4OTQ2MjI3Mnw4MzliNDg5NS0wYg Bug: 1473556 Change-Id: I9124921d8d6499e50c1403f953c5c035a5a5eeef Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4798130 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Hadrien Jaubert <hadrienjaubert@google.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools