RPP: Reveal detail attached to extension events and hyperlink URLs
UI:
- If any custom data is attached to a measure/mark/timestamp, we'll now
render it.
- non-string data is now allowed, we'll reuse `renderObjectJson` for
rich object rendering
- Same for detail.devtools.properties[], little DX upgrade.
- Linkify any URLs found within attached data.
- If we find an object with keys `url` and `description`, they get their
own exclusive row in the summary UI
- Bugfix: extension perf.mark was being rendered with tooltip as its
name, rather than name.
Refactor/naming:
- The extension data (track, trackGroup, color) is kept together in a
devtoolsObj, renamed to distinguish from a generic `args`
- Any user-supplied data (via measure/mark `details` object, or 7th arg
of console.timeStamp()) is extracted into a userDetail object.
Bug: 436356278
Change-Id: Id75b92ac1b8c7801b08e2d154b18b40d723d0218
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6819859
Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org>
Auto-Submit: Paul Irish <paulirish@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Mathias Bynens <mathias@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.