[breakpoints] Add closest resolved location calculation to Breakpoint Introduce a public helper `Breakpoint.getClosestResolvedLocation()` which dynamically identifies the resolved location (UILocation) that is closest to the original breakpoint line/column where the user clicked. This calculates line distance first, then column distance. This API is designed to be shared by UI panels (like BreakpointsView and DebuggerPlugin) to cleanly de-duplicate multiple resolved locations while natively preserving correct visual breakpoint sliding. Also adds robust unit tests covering this model-level selection logic. R=alexrudenko@chromium.org Bug: 493674242 Change-Id: Ia5ddf49fbca312e38a5501e811e340cda66677e3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7883002 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Simon Zünd <szuend@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.