Closed Bug 1861567 Opened 2 years ago Closed 2 years ago

Firefox dev tools network panel doesn't respond after resizing details pane

Categories

(DevTools :: Netmonitor, defect)

Firefox 120
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1530605

People

(Reporter: sekhar, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0

Steps to reproduce:

Open developer tools, select network tab, visit a page, and select a request - the details pane opens showing Headers, Cookies, etc. Now try to resize this details pane (I'm using a Wacom tablet, if that is the issue).

Actual results:

The pane will start resizing and then stop, with the cursor turning into the arrows mode. After that point the cursor remains that way and neither the network panel nor the details pane respond. The only way out is to refresh the page.

Expected results:

The details pane should have resized and the pane and the network panel should have continued to respond normally.

Component: Untriaged → Netmonitor
Product: Firefox → DevTools

Thank you for the report!

I can't reproduce the problem on my machine Win 11 (desktop) and I don't recall having such problem in the past. It feels like it might be related to the Wacom tablet and bug 1530605. Can you please look at that other bug and see if it can be related?

Flags: needinfo?(sekhar)

Thanks, yeah it seems to be related in that the behavior is similar. Unfortunately though the workarounds indicated there (turning off Windows ink and turning on dom.w3c_pointer_events.dispatch_by_pointer_messages) did not help. I'd appreciate any other pointers you may have. Thanks!

Flags: needinfo?(sekhar)

Thank you for the response!

I am closing this bug as dup of the bug 1530605. I don't have any tips about how to fix this, but please ask in the other but. It might be also useful to provide your STRs there!

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1530605
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.