Add DOMTreeWidget unit test screenshots for tree states This adds comprehensive unit test screenshots for DOMTreeWidget covering expanding, collapsing, editing, and highlighting states in both default and declarative tree modes. To prevent test flakiness, animations and cursor blinking in CodeMirror editors are suppressed during screenshot capture, and editing sessions are properly cleaned up in try-finally blocks. Bug: None Change-Id: I35a9498b246473aecd7796e652b678710f77d7f4 TAG=agy CONV=f3591f15-4c69-4118-b344-66c0be2bd68e Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8395208 Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.