commit | eba6371f39ac59cd197b364189bc189df85cfe8f | [log] [tgz] |
---|---|---|
author | Philip Pfaffe <pfaffe@chromium.org> | Mon Sep 23 12:56:53 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 26 08:29:25 2024 |
tree | 57286a6df3aea215b753352e9bc01add5b5f84e4 | |
parent | ccd44cd8dae3f472ff48afc350018e0d1dde6776 [diff] |
Resolve css keywords CSS-wide keywords (unset, initial, inherits, revert, revert-layer) are ways to set property values relative to a different context. In order to correctly compute variable values we need to be able to resolve these values. Fixed: 40280717, 40706051 Change-Id: I110ed8258b55f900d68d5ecdcb16d9a9537e89ec Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5788602 Reviewed-by: Changhao Han <changhaohan@chromium.org> Commit-Queue: Philip Pfaffe <pfaffe@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.