[RPP] Fix trace event search issues 1. The search feature was doing nothing if the query was <3 characters. This produced confusing results when deleting your query, since the last result highlights still lingered. 2. Ending the search sometimes threw an error from accessing a trace event indexed by -1. This resulted in search highlights remaining until the next time the panel was redrawn. TypeScript didn't catch this, because it was a normal array access. Fixed this by making the type nullable, instead of using -1 to denote "no selection". Bug: 373914908 Change-Id: Ib292054a47b99c39dc36fdc459d8b44adb7ba044 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5939712 Auto-Submit: Connor Clark <cjamcl@chromium.org> Reviewed-by: Paul Irish <paulirish@chromium.org> Commit-Queue: Paul Irish <paulirish@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.