[network] Implement parser for text/event-stream protocol This CL is basically a port of blink's event_source_parser.cc [1]. The problem is that the backend parser only kicks in if a page actually uses the "EventSource" object. Web pages that use text/event-stream without "EventSource" (e.g. via fetch/XHR) don't get the corresponding CDP events. We'll hook up the added parser in a follow-up to bytes received via "Network#dataReceived" once "Network#streamResourceContent" has landed. The parsed events will then be forwarded to the already exising EventSource UI. [1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/eventsource/event_source_parser.cc R=alexrudenko@chromium.org, mathias@chromium.org Bug: 1025893 Change-Id: I31d0fff2fb9cf7fab506674f08c69b4840a69c3c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5092889 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Mathias Bynens <mathias@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 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