Closed Bug 1942072 Opened 1 year ago Closed 1 year ago

long Integers rounding last two digits to '00' in parsed Request/Response JSON in Netmonitor

Categories

(DevTools :: Netmonitor, defect, P2)

defect

Tracking

(firefox137 fixed)

RESOLVED FIXED
137 Branch
Tracking Status
firefox137 --- fixed

People

(Reporter: nchevobbe, Assigned: nchevobbe)

References

Details

Attachments

(1 file)

Steps to reproduce

  1. Navigate to https://fx-devtools-netmonitor-json-lossy-number.glitch.me/
  2. Open Netmonitor
  3. Click on the "fetch JSON" button in the page
  4. Select the request in Netmonitor, and select the Response tab (same issue can be seen in the Request tab as the fetch call has a JSON body)

Expected results

The parsed JSON values are the same as the response

Actual results

The values are truncated because we're using JSON.parse (same cause as in JSON Viewer)


What we're doing for the JSON Viewer in Bug 1431808 should be easy to apply to the Netmonitor as well

Severity: -- → S3
Priority: -- → P2

This is doing the same thing we added not long ago in the JSON Viewer.

Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cefe052b69df [devtools] Display JSON source number when it's different from JS parsed value in Netmonitor. r=devtools-reviewers,jdescottes

Backed out for causing dt failures on browser_metrics_webconsole.js

Backout link

Push with failures

Failure log // Failure log 2

Flags: needinfo?(nchevobbe)

fixed the issue

Flags: needinfo?(nchevobbe)
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5ec455785075 [devtools] Display JSON source number when it's different from JS parsed value in Netmonitor. r=devtools-reviewers,jdescottes
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Regressions: 1965996
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: