Closed Bug 1622617 Opened 5 years ago Closed 5 years ago

Cannot see raw data of websocket frames

Categories

(DevTools :: Netmonitor, defect, P1)

defect

Tracking

(firefox-esr68 unaffected, firefox74 wontfix, firefox75- verified, firefox76 verified)

VERIFIED FIXED
Firefox 76
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- wontfix
firefox75 - verified
firefox76 --- verified

People

(Reporter: pranavpandey1998official, Assigned: bomsy)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0

Its very strange , I could see the element in the browser toolbox, https://www.youtube.com/watch?v=NO7jFcoID8s

Hi,

I was able to reproduce this issue on Windows 10 with Firefox version Nightly 76.0a1 (2020-03-18) (64-bit) - Beta 75.0b5 (64-bit) - Release 74.0 (64-bit). Marking those flags as affected.

Also I'm setting component to Devtools - Netmonitor and status to NEW for someone to take a look at this.

Status: UNCONFIRMED → NEW
Component: Untriaged → Netmonitor
Ever confirmed: true
Product: Firefox → DevTools
Version: 73 Branch → Trunk

Bomsy, could this be accordion related? It doesn't seem to be a regression.

The content appears with the following change, which is strange as the textarea inside .accordion-content has a height.

/* Accordion.css | resource://devtools/client/shared/components/Accordion.css */

.accordion-content {
  /* overflow: auto; */
}

Flags: needinfo?(hmanilla)

Yeah it is accordion related. It is probably a regression from the response panel work.

Here is the css that causes the issue
https://searchfox.org/mozilla-central/rev/6cd54550a27e2f6ca0755a25328f769e41e524f4/devtools/client/netmonitor/src/assets/styles/NetworkDetailsBar.css#75

Flags: needinfo?(hmanilla)
Regressed by: 1613885

Thanks Hubert for the analysis!

Mark as P1, this should be fixed asap and feels like we know what to do.

Honza

Priority: -- → P1
Summary: Cannot see raw data of websocket frams → Cannot see raw data of websocket frames
Assignee: nobody → hmanilla
Pushed by hmanilla@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b3eb47d62fa0 Fixed showing the websocket frames r=Honza
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 76

[Tracking Requested - why for this release]: Small fix that avoid loosing data in the UI.

Please request beta uplift when you get a chance.

Flags: needinfo?(hmanilla)

Comment on attachment 9134664 [details]
Bug 1622617 - Fixed showing the websocket frames r=honza

Beta/Release Uplift Approval Request

  • User impact if declined: Impacts only developers, websocket frames not showing
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Only affects developers, small patch, only css changes
  • String changes made/needed:
Flags: needinfo?(hmanilla)
Attachment #9134664 - Flags: approval-mozilla-beta?

I should maybe have caught this earlier, but... this bug is set as "regressed by 1613885". Bug 1613885 is only in 76. How is 75 even affected here?

Flags: needinfo?(hmanilla)

Oh yeah .. that is correct! missed that.
harald do you agree?

Flags: needinfo?(hmanilla) → needinfo?(hkirschner)

I saw this on 75 as well, and so states comment 5 as well, so I am not sure if this is a regression. Would the uplift improve this for 75?

Flags: needinfo?(hkirschner)

Based on comments 2/3/14 I'll clear the regression info here.

Keywords: regression
No longer regressed by: 1613885

Comment on attachment 9134664 [details]
Bug 1622617 - Fixed showing the websocket frames r=honza

approved for 75.0b10, but asking for verification.

Attachment #9134664 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Flags: qe-verify+
QA Whiteboard: [qa-triaged]

Hi,

I was able to reproduce this issue on Firefox version 74. And then I was able to verify the fix on Windows 10, Mac OS 10.14 and Ubuntu 18, with Firefox version Nigthly 76.0a1 - Build ID 20200327094805 and Beta 75.0b10 Build ID 20200326191140. Making those flags as verified.

Also I'm setting status to VERIFIED and removing [qa-triaged] and qe-verify+ flags.

Thanks.

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triaged]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: