* Remove ability to load log files. Instead refer developers/users to http://catapult-project.github.io/catapult/netlog_viewer (Ability to save log files should already have been removed)
* Remove visualizers for the NetLog event stream (i.e. #events tab)
* Remove real-time viewing of events and polled data
All that will be left in chrome://net-internals/ after this is chrome://net-internals/#hsts, the Chrome OS stuff, and perhaps some of the action buttons (clear cache, flush sockets, etc).
The rest will be subsumed by chrome://net-export + net log viewer app.
* Remove ability to load log files. Instead refer developers/users to the net log viewer app (Ability to save log files should already have been removed)
* Remove visualizers for the NetLog event stream (i.e. #events tab)
* Remove real-time viewing of events and polled data
All that will be left in chrome://net-internals/ after this is chrome://net-internals/#hsts, the Chrome OS stuff, and perhaps some of the action buttons (clear cache, flush sockets, etc).
The rest will be subsumed by chrome://net-export + net log viewer app.
Eric & Emily: do we need the Domain Security Policy parts, i.e. the HSTS/PKP & Expect-CT section? I'm wondering if they're used and so we need to convert them to work with out-of-process networking, or we can remove them?
I'll defer that answer to Emily or Chris.
I believe #hsts is the only way to look at that data right now, and is used, so that or something analogous will be needed.
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.
All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.
Thanks for your time! To disable nags, add the Disable-Nags label.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
[dxie]: Per the email I sent you earlier, release blocker means stable should not be released without this fixed. I believe you attached the label meaning that the network service shouldn't go to stable without this fixed, which is not what the label means.
Comment 1 by mmenke@chromium.org
, May 24 2018Labels: Proj-Servicification