1328939 - Selection in inspector sidebars extends outside of scrollable part, so keyboard scrolling doesn't work

Status: RESOLVED WONTFIX

(DevTools :: Inspector, defect)

Description

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

+++ This bug was initially created as a clone of Bug #1327771 +++

>>>   My Info:   Win7_64, Nightly 52, 32bit, ID 20161028030204 (2016-10-28)
Text selection in console and inspector extends to outside of scrollable part.
And that, in turn causes these issues:
- (1) Up/Down/PageUp/PageDown/Home/End buttons don't work
- (2) filter buttons / tabs in inspector become selected
- (3) Ctrl+Shift+Home/End doesn't scroll srollable area to the beginning/end
This can be resolved by using iframes. Proof of concept:
data:text/html,asdf<iframe src="http://example.org"></iframe>zxcv

==== Inspector sidebars ====
STR_4:
1. Open url [1]
2. Open inpector -> rules, select text "max-height: 2099px;" with mouse
3. Press Ctrl+A to select all text in ruleview
4. Press Up/Down keys, or PageUp/PageDown, or Home/End to scroll rules via keyboard

AR:  No visible action
ER:  Rules should scroll up/down


STR_5:
1. Open url [1]
2. Open inpector -> rules, select text "max-height: 2099px;" with mouse
3. Press Ctrl+A

AR:  Tabs in inspector sidebar become selected
ER:  Text selection shouldn't extend to tabs


STR_6:
1. Open url [1]
2. Open inpector -> rules, select text "max-height: 2099px;" with mouse
3. Press Ctrl+Shift+Home/End

AR:  Scroll position in ruleview doesn't change
ER:  Rules should be scrolled to the beginning/end


STR_7:
1. Open url [1]
2. Open inpector -> rules, select text "max-height: 2099px;" with mouse from right to left
3. Press Ctrl+Shift+Home

AR:  All text AFTER "max-height: 2099px;" is selected(!)
ER:  All text from beginning to "max-height: 2099px;" should be selected

Comment 1

[castiel743]

These 2 bugs (bug 1328938, bug 1328939) were originally filed by arni2033 as bug 1327771.
It doesn't look like they will live well separately (w/o general decision on how to fix such things),
and it doesn't seem that there was a good reason to resolve original report as Invalid.
After all, reporter of that bug was concerned about usability, not about stealing bugs.

The correct way to track a meta bug is to keep it open until all blocking bugs are resolved.

Comment 2

[Patrick Brosset <:pbro>]

Sorry will have to close this one. I can't reproduce at the moment.