Open
Bug 1276123
Opened 10 years ago
Updated 3 years ago
It's possible to accidentally focus multiple nodes simultaneously
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
NEW
People
(Reporter: arni2033, Unassigned)
Details
Attachments
(2 files)
>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160526082509
STR:
1. Open page data:text/html,<style>body{background:none;border:none}
2. Open inspector, click on `<body>`. Press Tab several times to focus "background" in ruleview.
3. Press Spacebar to start editing, then press Ctrl+L to focus urlbar.
4. Press Shift+Tab several times to focus first `none` in ruleview.
[bonus]
5. Repeat Step 3.
6. Press Shift+Tab several times to focus `border` in ruleview.
7. Repeat Step 3.
8. Press Shift+Tab several times to focus second `none` in ruleview.
AR: Many nodes are focused at once. Before bug 1242694 it was possible to do the same in markup.
ER: This must be impossible.
Please set an appropriate component.
Comment 1•10 years ago
|
||
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
I have managed to reproduce this issue on Windows 10 x64 and Ubuntu 15.04 x64 using the latest Firefox release (46.0.1, Build ID 20160502172042) and the latest Nightly (49.0a1, Build ID 20160530071207).
Component: Untriaged → Developer Tools: Inspector
Product: Core → Firefox
(this is what happens in STR_1)
STR_2:
1. Open attached "testcase 1"
2. Focus the 1st empty button on the page by pressing Tab key
3. Click on "hide" button
4. Click in searchbar
5. Click on "hide" button
6. Click on the 2nd empty button on the page
AR: Both empty button look focused
ER: Only 1 button should look focused at the same time
I will undo priority now, because it was set by devtools team.
Component: Developer Tools: Inspector → XP Toolkit/Widgets: XUL
Priority: P3 → --
Product: Firefox → Core
Comment 5•8 years ago
|
||
Moving to Core:XUL per https://bugzilla.mozilla.org/show_bug.cgi?id=1455336
Component: XP Toolkit/Widgets: XUL → XUL
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•