Preview tab is not automatically parsing JSON and not displaying it formatted.
Reported by
andrei.l...@gmail.com,
Nov 1
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. View an XHR call in the Network Tab 2. Click Preview 3. See how it does not automatically parse the JSON to be presented formatted and pretty like it usually does. What is the expected behavior? The JSON should be formatted and collapsible. What went wrong? The JSON is just a text blob. Did this work before? Yes 69 Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: The same problem was described in https://bugs.chromium.org/p/chromium/issues/detail?id=767393
,
Nov 1
,
Nov 2
Thanks for the report. DevTools uses some heuristics to guess whether it can format as JSON, including some cases where there is no Content-Type. To help us reproduce, do you have a sample site/html/HAR other details about this response you can provide?
,
Nov 2
,
Nov 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 5
andrei.lomako.idf@ Thanks for the issue. Able to reproduce the issue on Windows 10 and Mac OS 10.13.6 on the reported version 70.0.3538.77. Issue seems to be fixed on the latest canary 72.0.3602.0. Will provide the Bisect info soon. Hence marking the issue as Untriaged. Thanks..
,
Nov 6
//Adding to comment #7 Able to reproduce this issue on Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 on the latest Stable 70.0.3538.77. Issue seems to be fixed on the latest Canary 72.0.3602.2 and Beta 71.0.3578.30. Reverse Bisect Information: ============================ Good Build: 71.0.3577.0 Bad Build : 71.0.3576.0 By running the per-revision bisect script, below is the Changelog URL. https://chromium.googlesource.com/chromium/src/+log/4b582326361faa7bb7d8a204af98d55cb4b6a1f0..5b046432f18e81cc58d32191c8a8ad150c8b74ad From the above Changelog, suspecting the below Change. Reviewed-on: https://chromium-review.googlesource.com/c/1230042 Unable to assign the bug to the author ingvar@cloudflare.com. Hence assigning the bug to reviewer dgozman@. dgozman@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks...
,
Nov 6
,
Nov 6
Joey, could you please confirm this is fixed in 71 and close?
,
Nov 6
By using andrei.lomako.idf@'s LoginPageHAR as a sample json file to be served and requested via fetch(), I can confirm that 70.0.3538.0 does not parse it as JSON and 71.0.3578.0 does properly parse it as JSON. Since the reporter also confirmed that the bug is fixed in 71.0.3578.30, I will close the bug. However, I found that 69.0.3497.0 did not parse the JSON, despite andrei.lomako.idf@ reporting that it did in 69. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by andrei.l...@gmail.com
, Nov 1