Open
Bug 1395193
Opened 7 years ago
Updated 2 years ago
Screen don't move up or down in DOM section when pressing keyboard's up or down key
Categories
(DevTools :: DOM, defect)
DevTools
DOM
Tracking
(firefox-esr52 unaffected, firefox56 fix-optional, firefox57 fix-optional)
NEW
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox56 | --- | fix-optional |
firefox57 | --- | fix-optional |
People
(Reporter: mAlmas, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
5.48 MB,
video/mp4
|
Details |
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•7 years ago
|
||
Updated•7 years ago
|
Component: Untriaged → Developer Tools: DOM
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
Comment 2•7 years 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.
Updated•7 years ago
|
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: minor → S4
status-firefox55:
wontfix → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•