Open
Bug 1250016
Opened 10 years ago
Updated 1 year ago
Modal dialog doesn't completely steal focus in some cases allowing to perform keyboard actions with browser
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox47 | --- | affected |
People
(Reporter: arni2033, Unassigned)
References
(
URL
)
Details
(Whiteboard: tpi:+)
>>> My Info: Win7_64, Nightly 47, 32bit, ID 20160218030349
STR:
1. Launch new profile, open some new tabs (non-pinned). Open this "data:" url in a new tab:
> data:text/html,<style>body{ height:10000px; }
2. Make sure that firefox window is focused. Maximize it. Make sure that it's the only firefox window
3. Hover mouse over the firefox button on Windows' taskbar.
4. Wait until previews appear (you can see what "preview" is on screenshot in bug 1202181)
5.A) Click "Close" button in that preview [modal dialog "You are about to close N tabs" will appear]
5.B) Right-click the preview, then click "Close" menuitem.
6. Press Up/Down, then press Ctrl+Tab several times
AR:
(A) In Step 6, pressing Up/Down scrolls the page up/down. Pressing Ctrl+Tab changes selected tab.
(B) In Step 6, pressing Up/Down does nothing. Pressing Ctrl+Tab does nothing.
ER:
They should work the same way in scenarios (A) and (B)
Comment 1•10 years ago
|
||
It looks if you go through scenario 5A the modal dialog doesn't have focus by default, and so user input still goes to the Firefox window. In scenario 5B the modal dialog does get focus by default. In 5A if you click on the modal dialog once it comes up, focus is locked to the modal dialog and you can't repro the problem any more. It's just that initially when the dialog comes up it doesn't have focus.
I was able to repro this with and without e10s. It seems like a windows widgetry issue so I'm moving this to the appropriate component.
Component: Untriaged → Widget: Win32
OS: Unspecified → Windows
Product: Firefox → Core
Updated•9 years ago
|
Priority: -- → P3
Whiteboard: tpi:+
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•