[Elements] Use --sys-size-24 for style property editor min-width Snap .container min-width from 170px to var(--sys-size-24) (176px) in stylePropertyEditor.css so Flexbox, Grid, and Grid Lanes style property editor popovers comfortably fit 170px nowrap property labels and 168px 7-button rows without overflow or width jitter. Fixed: 552494326 Change-Id: I8978e8e30d8d7ba8e5512e3a9363ddd44d9737fe Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8724592 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Auto-Submit: Yang Guo <yangguo@chromium.org> Presubmit-Verified: devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
This repository contains the client side of Chrome DevTools. It contains all the TypeScript and CSS code that runs the DevTools web app.
The source code is on chromium.googlesource.com.
The Chromium DevTools documentation tells you how to do these tasks:
The documentation also contains design guidelines and architecture documentation.
Other documentation:
There is a mirror of the DevTools frontend repository on GitHub.
The DevTools frontend is also available on npm as the chrome-devtools-frontend package. The package does not supply CJS modules or ES modules. Thus, it can be difficult to use this package in other tools. For an example of how to use it, see this file.
The version number of the npm package (for example, 1.0.373466) is the Chromium commit position of the latest frontend Git commit. The version number increases with each Chromium commit. But we publish the package only approximately one time each day.
To get the latest news about DevTools development, do one or more of these steps:
Read What's new in DevTools.
Read Umar's Dev Tips.
Follow these accounts on X: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Join the g/devtools-reviews@chromium.org mailing list. This list shows all pending code reviews.
Read the commit log, or follow @DevToolsCommits on X.
See all open DevTools bugs on crbug.com.
Use Chrome Canary and try the experiments.