[CSSMatchedStyles] Do not bail out when getAnimatedStylesForNode errors Previously, we were returning `null` for `CSSMatchedStyles` creation when either `getMatchedStylesForNode` or `getAnimatedStylesForNode` errored. However, native UI DevTools do not implement `getAnimatedStylesForNode` CDP method; thus it causes `CSSMatchedStyles` to be not created since this method now errors. I have updated the logic to not bail out from `matchedStyles` creation for animated styles so that UI native DevTools still works. This also makes sense for the case where somehow `getAnimatedStylesForNode` returns an error (then we don't show the animated styles until it stops erroring after computed style updates) Fixed: 395131432 Change-Id: Ic12568467d0cd34ee95a836b94f52a1182945b8b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6243807 Commit-Queue: Philip Pfaffe <pfaffe@chromium.org> Auto-Submit: Ergün Erdoğmuş <ergunsh@chromium.org> Reviewed-by: 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.