Closed
Bug 1669693
Opened 5 years ago
Closed 5 years ago
WebSocket Messages keyboard navigation doesn't work
Categories
(DevTools :: Netmonitor, defect)
DevTools
Netmonitor
Tracking
(firefox83 fixed)
RESOLVED
FIXED
83 Branch
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: rockingskier, Assigned: rockingskier)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
When viewing the WebSocket messages panel you should be able to navigate up and down using keyboard shortcuts.
The issue is due to the action having the wrong signature. It is designed to work with thunk but netmonitor uses thunk-with-options.
(dispatch, getState) =>
({ dispatch, getState }) =>
Actual results:
Keyboard navigation has no effect.
Expected results:
Keyboard navigation should change the selected message
Comment 1•5 years ago
|
||
Thanks Ben! Do you want to be assigned to this bug as well?
Component: Untriaged → Netmonitor
Product: Firefox → DevTools
| Assignee | ||
Comment 2•5 years ago
|
||
Yes please. The fix is super quick. Just need to work on the test.
Updated•5 years ago
|
Assignee: nobody → rockingskier
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
| Assignee | ||
Comment 3•5 years ago
|
||
| Assignee | ||
Updated•5 years ago
|
Flags: needinfo?(odvarko)
Updated•5 years ago
|
Attachment #9180359 -
Attachment description: Bug 1669693 - fix WebSocket message keyboard navigation. r=honza,bomsy → Bug 1669693 - [devtools] fix WebSocket message keyboard navigation. r=honza,bomsy
Pushed by hmanilla@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5c95eb6e039a
[devtools] fix WebSocket message keyboard navigation. r=Honza,bomsy
Comment 5•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
Updated•5 years ago
|
Flags: needinfo?(odvarko)
You need to log in
before you can comment on or make changes to this bug.
Description
•