[RPP] Let NetworkHandlerHandler handle the cached event even if they don't have timing data Currently in TraceEngine, we will drop a request if it has no |timing| data. But those cached request could have no |timing| data. And how we do now is to calculate the |timing| related timestamp first from |timing|, and if they are cached, we overwrite them. To solve those problem, this CL does: - Only calculate the |timing| related data when the request is not cached. - Separated the calculated data and the original data from trace event. So the |args.data| can be served as source of truth. - Add a temporary test to check the network request is handled same as OPP. Bug: 1457485 Change-Id: Idf019955aa067cc64df8a456907a1bb75ec28e6c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4650354 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Nancy Li <nancyly@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