net-internals HSTS page disappears if you Stop network capture |
|||
Issue descriptionVersion: 49.0.2623.87 beta-m (64-bit) What steps will reproduce the problem? (1) Visit chrome://net-internals (2) Click Capture > Stop from the arrow at the top right (because I don't want to do a capture and the big red bar with increasing numbers on it is scary) (3) Click in the dropdown at the top left to look for the HSTS entry Expect: I can view HSTS information when capture is stopped. Actual: The HSTS element is hidden. If I directly navigate to chrome://net-internals#hsts, the UI appears but is non-functional. This problem seems to be rooted in the treatment of "Stop capture" as "Import capture" and importing a capture is meant to hide the HSTS node: https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/data/webui/net_internals/log_util.js&q=Waterfall%20HSTS&sq=package:chromium&type=cs&l=181
,
Mar 10 2016
This is working as intended behavior. Stop capture jettisons all code to talk to the browser, to keep things simple, and that includes the code to update all other tabs. I don't think there's any real need to fix this. Either we're displaying live data, or we're displaying logged data, and mixing the two is a bit weird.
,
Mar 11 2016
Thanks for the report! I agree with Eric that it is weird and we could do better. But I also agree with Matt's comment #2 that it isn't worth doing right now. The problem as I see it is more of an architectural one. With the current about:net-internals we are conflating a number of different things (capturing, inspecting live data, chromeos logging stuff, hsts editing). We start capturing by default when opening about:net-internals as a convenience to reduce the friction for the common case of having users capture a dump to send us. And the other panels kind of just grew out from that. In fact #hsts being a non-internationalized and non-accessibility-ized panel that we kind of maybe expect real users to employ is a separate problem in-of-itself ... Tentatively marking as WontFix per design suggestions in issue 473179 ... I've been wanting to burn about:net-internals to the ground for a while, but it not a high priority or even on my roadmap. (If about:net-internals is no longer capturing events, then this bug is solved)
,
Dec 9 2016
Security>UX component is deprecated in favor of the Team-Security-UX label |
|||
►
Sign in to add a comment |
|||
Comment 1 by rsleevi@chromium.org
, Mar 10 2016