[sources] Add 'Word wrap' setting for the Sources panel. This introduces a new setting to control word wrapping for the text editors in the Sources panel. The Elements panel already had this feature for the DOM tree and its inline editor. This also fixes the actions exposed via command menu and keyboard shortcuts to only show in the context of the relevant panels (previously the "Enable `DOM` word wrap" and "Disable `DOM` word wrap" actions were also shown in the Sources panel, which was very confusing). Fixed: 384940843 Change-Id: Ibffb6d22f860a1c79572692fa87c7c2b66301bcb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6494548 Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@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.