Screen don't move up or down in DOM section when pressing keyboard's up or down key

NEW
Unassigned

Status

()

Firefox
Developer Tools: DOM
--
minor
2 months ago
2 months ago

People

(Reporter: mAlmas, Unassigned)

Tracking

({regression})

Trunk
regression
Points:
---

Firefox Tracking Flags

(firefox-esr52 unaffected, firefox55 wontfix, firefox56 fix-optional, firefox57 fix-optional)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce:

1.Open Dev Tools(Inspect Element)
2.Go to settings
3.Check or enable DOM
4.Go to DOM tab besides Storage
5.Click any line in the DOM section
6.Pressing Keyboard's up or down key till it passes the end of the screen of DOM section 


Actual results:

As pressing the up or down key, selection of a line go up or down. When it reach the end of the screen of the DOM section, it continues it's selection but the screen of the DOM section don't move up or down.


Expected results:

The screen should move as the selection goes up or down till the end of the screen.
(Reporter)

Comment 1

2 months ago
Created attachment 8902729 [details]
DOM.mp4

Updated

2 months ago
Component: Untriaged → Developer Tools: DOM

Updated

2 months ago
Severity: normal → minor
Status: UNCONFIRMED → NEW
Has STR: --- → yes
status-firefox55: --- → affected
status-firefox56: --- → affected
status-firefox57: --- → affected
status-firefox-esr52: --- → unaffected
Ever confirmed: true

Updated

2 months ago
Blocks: 1335192
Has Regression Range: --- → yes
Keywords: regression

Comment 2

2 months ago
Yes this is because of the display CSS value for the dom panel tree container. Inspector works well with this keyboard interaction and it is because it uses scroll on move utility with the right CSS styling for the tree container.
status-firefox55: affected → wontfix
status-firefox56: affected → fix-optional
status-firefox57: affected → fix-optional
You need to log in before you can comment on or make changes to this bug.