Notifications shouldn't apply focusring to the next element if I click close button

NEW
Unassigned

Status

()

Core
XUL
P5
normal
a year ago
22 days ago

People

(Reporter: arni2033, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox56 wontfix, firefox57 wontfix, firefox58 wontfix, firefox59 ?)

Details

(Reporter)

Description

a year ago
>>>   My Info:   Win7_64, Nightly 52, 32bit, ID 20161001030430 (2016-10-01)
STR_1:
1. Launch Nightly 2016-05-26 via mozregression GUI
2. Wait about 1 minute until notification appears at the bottom of the window
3. Click on close button in notification

AR:  Selected tab in tabs toolbar displays focusring. See Note 1 to understand why it's bad
ER:  No focusring in current tab. 


Notes:
1) If <tab> in tabs toolbar is focused, it won't return focus to element on the page when I switch to
   another tab via Ctrl+Tab. Therefore focused element is lost, so I have to focus it again. Examples:
  1.1) Youtube: When I watch playlists/listen music playlists in background, I always keep "Next"
       button in youtube video controls focused, to have a working shortcut "Enter key navigates
       to the next video". (Other hotkeys already exist, e.g. "Alt+Left navigates to previous video")
       I may need to immediately switch to tab and navigate to the next video in playlist.
  1.2) Bugzilla: When I file several bugs in a row, or even several comments in a row, I open
       several tabs, fill all the fields necessary and focus "Submit Bug" / "Save Changes" button.
       I may need to immediately switch to tab and press the button via Spacebar.
  1.3) VK.COM: https://vk.com/ is a russian social network, a Facebook clone.
       I have a special tab with personal messages. If the page is focused, typing anything
       automatically focuses input field, so I can easily send messages w/o focusing the input field
       directly. However, for that to work, at least the page itself must be focused.
(Reporter)

Updated

a year ago
No longer blocks: 1277113
(Reporter)

Updated

a year ago
Component: Untriaged → XP Toolkit/Widgets: XUL
Product: Firefox → Core

Comment 1

8 months ago
Not sure what notification is being referred to here.
status-firefox56: --- → wontfix
status-firefox57: --- → wontfix
status-firefox58: --- → fix-optional
Priority: -- → P5
Moving to Core:XUL per https://bugzilla.mozilla.org/show_bug.cgi?id=1455336
Component: XP Toolkit/Widgets: XUL → XUL
You need to log in before you can comment on or make changes to this bug.