chrome://net-internals/ Capture dialog does not obtain capture file name from user
Reported by
jidanni@gmail.com,
Feb 11 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: Visit chrome://net-internals/ Click Capture. After a while click Stop. The problem is no file name for the capture has been set! The bytes have been captured, but there is no way to access / save them. The correct procedure would be: Visit chrome://net-internals/ Click Capture. At this point the browser should redirect to the chrome://net-export/ dialog. That dialog properly obtains a filename from the user in which to save the capture. What is the expected behavior? Captured bytes placed somewhere. What went wrong? Captured bytes inaccessible. Did this work before? N/A Chrome version: 64.0.3282.119 Channel: n/a OS Version: Flash Version:
,
Feb 12 2018
,
Feb 12 2018
Thanks for the report! As you have noted, chrome://net-export/ is the supported way documented at https://dev.chromium.org/for-testers/providing-network-details for saving logs to a file. I don't think we need to add more clarifications on chrome://net-internals#capture given that it will be removed in the future (issue 472699).
,
Feb 13 2018
OK good. I'm just saying many people end up using these entry point URLs from snippets on StackExchange, etc. you never know, and thus would never find the expected documentation's route. |
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Feb 11 2018