[elements] Make the expand button of collapsed DOM tree nodes work again The "…" button rendered after a collapsed element's opening tag used to call the TreeElement's expand() through a hook on the widget. That hook stopped being set when the legacy ElementsTreeOutline was deleted, so clicking the button only selected the node. DOMTreeElementWidget now exposes an expandNode callback that the button invokes, and DOMTreeWidget wires it to the same onExpand path that the tree item's expand event uses (and only for collapsible nodes, like that path). Adds a widget-level and a tree-level unit test for the button. Bug: 407751692 Change-Id: I0129e5460ccc9cd04cc49c79bd61df2238f31e24 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8564098 Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Simon Zünd <szuend@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.