[elements] Update working copy from Styles tab. When modifying CSS, the Styles tab previously wrote straight to disk when a workspace folder was connected, instead of updating the working copy (like the Sources panel does). This is a very inconsistent and confusing behavior, and doesn't align with the intended use cases that we're working on for Workspace feature. Also show an asterisk in the Styles tab for modified CSS files, similar to what we do in the Sources panel. Bug: 405312529 Screenshot: https://i.imgur.com/iXDyU1S.png Change-Id: I980cb87a8d985f4cab6b6b26fa2618ee6001d24c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6382153 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Ergün Erdoğmuş <ergunsh@chromium.org> Commit-Queue: Ergün Erdoğmuş <ergunsh@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.