Revert "Do nothing in SplitWidget.showBoth if already showing" This reverts commit 250194ed20869038dbb01602b259605471289601. Reason for revert: causes http://crbug.com/404476981 - "Unable to drag the devtools while panel is at left side" Original change's description: > Do nothing in SplitWidget.showBoth if already showing > > This method resulted in some unnecessary work happening in RPP, causing > the flame graph to respond to a "resize" event even though nothing > changed size. Since RPP calls this often (like when activating an > insight), this contributed to the sometimes-janky feeling caused by > opening an insight taking too long. > > Bug: 40278532 > Change-Id: I43b4d4e7a9b400cd3edf06f3f606e008b6455c2d > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6221819 > Commit-Queue: Connor Clark <cjamcl@chromium.org> > Reviewed-by: Paul Irish <paulirish@chromium.org> Bug: 40278532, 404476981 Change-Id: I1b144d662dd537d397c6c61c6abc1ae9be3c5d4a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6369954 Reviewed-by: Paul Irish <paulirish@chromium.org> Commit-Queue: Connor Clark <cjamcl@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.