Closed Bug 1716245 Opened 4 years ago Closed 4 years ago

Wrong encoding in JSON response view

Categories

(DevTools :: Netmonitor, defect, P3)

Product:
DevTools
Component:
Netmonitor
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sebo, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

The formatted JSON view

  1. Go to https://docs.microsoft.com/zh-cn/dotnet/breadcrumb/toc.json
  2. Open the Netmonitor
  3. Reload the page
  4. Select the request for the file
  5. Switch to the Response view
  6. Search for "C#"

What happened?

The value of the toc_title property looks garbled. It is obviously encoded incorrectly.

What should have happened?

The characters of the value should be shown correctly.

Anything else we should know?

This was initially reported by ylxianzhe in Discourse.
I've tested it in today's Nightly on Windows 10.

Interestingly, the JSON Viewer (outside of the Netmonitor) doesn't seem to be affected by that.

Sebastian

Thanks for reporting.

I can reproduce it.

Blocks: netmonitor-response-sidepanel
Severity: -- → S3
Priority: -- → P3

Bomsy, ylxianzhe mentioned a week ago that the problem is gone. I've tested it right now in Firefox 90 and also cannot reproduce it anymore. Interestingly, I also cannot reproduce it anymore using the previous Firefox versions 89 and 88 where it constantly failed before.

Do you see the same? And if so, any idea what could have fixed it?

Ylxianzhe, is the issue also gone for the other site where you originally experienced that bug?

Sebastian

Flags: needinfo?(ylxianzhe)
Flags: needinfo?(hmanilla)

Hello,Sebo.
I spent the whole morning browsing Chinese information on the Internet, but did not find another similar url. The bug was not reproduced on the website where I originally found the bug. In fact, this is the normal state of this bug. It appears occasionally. I have never seen a URL that reproduces bugs like Microsoft.
I will still try to find a URL that can reproduce this bug. If found, I will use wireshark to grab the network request. This might be useful.

I've tested this again using Firefox 96.0 and still can't reproduce this. Therefore I close this bug now.
If anyone has a new test case for which it can constantly be reproduced, we can reopen it.

Sebastian

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(ylxianzhe)
Flags: needinfo?(hmanilla)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.