[formatter] Avoid spurious line breaks after inline HTML elements Previously, HTMLFormatter.#afterCloseTag unconditionally inserted a newline after every closing tag, even for leaf elements without child elements. When a leaf element was followed by text on the same line (such as `<span>Some text</span>}` or `<li> hello <b>world</b>!`), the trailing text was forced onto a new line. Update #afterCloseTag to skip adding a newline when a leaf element is followed by inline text (either directly or after horizontal whitespace on the same line). R=kimanh@chromium.org Fixed: 388055639 TAG=agy CONV=f1f9f717-124c-4523-ba24-a08b1b90dea7 Change-Id: I68f1b27cad9787b0239ca0c1a09d42b83b52d992 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8549245 Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Kim-Anh Tran <kimanh@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.