[CLSCulprits] Ensure insight is visible when CLS is not 0 The insight state should be the same as the `layout-shifts` LH audit: - Pass if CLS score is 0 - Informative if CLS score is "good" but not 0 - Fail if CLS score is not "good" This also modifies the sidebar component to always show the link to the largest cluster even if no specific culprits were found. CLS is nonzero but no culprits: https://screenshot.googleplex.com/9hTsZE3Na5qEguX CLS is nonzero with culprits: https://screenshot.googleplex.com/SNETHuNCUYQJEyk Bug: 388723721 Change-Id: I22ba039e87a8baeaedd98492765633b4b3a0d041 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6303301 Commit-Queue: Adam Raine <asraine@chromium.org> Reviewed-by: Adriana Ixba <aixba@chromium.org> Reviewed-by: 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.