Avoid taking screenshots on ScreenshotErrors This fixes a bug where after a screenshot error the `onError` handler would take a pair of target/frontend screenshots and obscure the original error. Behaviour before the fix: https://luci-milo.appspot.com/ui/inv/u-liviurau-2023-09-28-11-48-00-7335b87ae21fb818/test-results Behaviour after the fix: https://luci-milo.appspot.com/ui/inv/u-liviurau-2023-09-28-12-01-00-5cb60fc22ac97b0d/test-results Bug: none Change-Id: I6f86d89f1476adeb3a3ad9513f0d5c472410ea8f Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4900637 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Eric Leese <leese@chromium.org> Commit-Queue: Eric Leese <leese@chromium.org> Auto-Submit: Liviu Rau <liviurau@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
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