Remove `setNavStart` method from minimap and use new engine This CL updates the TimelineMiniMap to use the new engine for its navigation events. We remove the explicit method that was used to set the navigation start events, and instead calculate them via the new engine. I also renamed the MiniMap `updateControls` method to `setData` to better reflect what it does. After this CL the old engine's tracking of navigation start events is entirely unused; I will therefore remove it but do so in a follow-up to avoid this CL getting too large. Bug: 1464206, 1472229 Change-Id: If5379434b8ea91504b3783b97f92b5fc7b4c127f Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4774407 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Paul Irish <paulirish@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools