Mark UISourceCode as synthesized in StyleFile.addHeader Previously, StylesSourceMapping only called NetworkProject.setSourceURLSynthesized when a StyleFile was initially constructed. If a stylesheet without a sourceURL comment was added first and a synthetic stylesheet with a /*# sourceURL=... */ comment for the same URL was added later via StyleFile.addHeader, the UISourceCode remained unflagged even after the original stylesheet was removed. Update StyleFile.addHeader to also mark the UISourceCode as having a synthesized sourceURL when header.hasSourceURL is true, and add a regression unit test. Bug: 562233597, 568225269 Change-Id: Ie8bb7d38207987431c9823676cd6ec38bf514aa2 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8518358 Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Eric Leese <leese@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.