commit | 8aef901f3f53d6091ee6b5d6616b8d9608a2748c | [log] [tgz] |
---|---|---|
author | Paul Lewis <[email protected]> | Tue Oct 29 14:15:17 2019 |
committer | Commit Bot <[email protected]> | Tue Oct 29 14:36:57 2019 |
tree | 4a80e7d4d2563aea19c9f2419bed3cf799bcc2de | |
parent | a2ca5d5c442a1ff23ff228af8c0143887f6722a6 [diff] |
[CSSOverview] Add unused rules This is the first pass at adding unused rules to the CSS Overview. The CL adds support for checking width & height to inline elements as well as position values to static elements. Further CLs will add additional checks for other cases, e.g. the use of flex or grid values against non-flex and non-grid elements respectively. Change-Id: I2fb4fd557d67065a5753587624195920c22b3edc Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1886818 Commit-Queue: Paul Lewis <[email protected]> Reviewed-by: Tim van der Lippe <[email protected]>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
As standalone project, Chrome DevTools front-end can be checked out and built independently from Chromium.
Get depot_tools first.
mkdir devtools cd devtools git clone https://chromium.googlesource.com/devtools/devtools-frontend gclient config https://chromium.googlesource.com/devtools/devtools-frontend --unmanaged
cd devtools-frontend gclient sync gn gen out/Default autoninja -C out/Default
To run the production build, use
<path-to-chrome>/chrome --custom-devtools-frontend=file://$(realpath out/Default/resources/inspector)
To run the debug build (directly symlinked to the original unminified source files), build both Chromium and DevTools frontend with the GN flag debug_devtools=true
, and use
<path-to-chrome>/chrome --custom-devtools-frontend=file://$(realpath out/Default/resources/inspector/debug)
DevTools frontend can also be developed as part of Chromium.
Follow instructions to check out Chromium. DevTools frontend can be found under chromium/src/third_party/devtools-frontend/src/
.
Refer to instructions to build Chromium. To only build DevTools frontend, use devtools_frontend_resources
as build target.
Change your working directory to the integrated DevTools frontend:
cd path/to/chromium/src/third_party/devtools-frontend/src
Add standalone DevTools frontend as remote:
git remote add standalone file://path/to/devtools/devtools-frontend/ git fetch standalone git checkout standalone/branch-of-your-choice
npm run format-py
Formats your Python code using yapf
Note: Yapf is a command line tool. You will have to install this manually, either from PyPi through
pip install yapf
or if you want to enable multiprocessing in Python 2.7,pip install futures
DevTools frontend is available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES2015 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.
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools