Closed
Bug 1496834
Opened 6 years ago
Closed 5 years ago
Windows 10 ToastNotifications do not focus Firefox when clicked
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect, P1)
Tracking
(firefox-esr60 unaffected, firefox-esr68 disabled, firefox63 unaffected, firefox64 disabled, firefox65- disabled, firefox66- disabled, firefox67- disabled, firefox68 disabled, firefox69 disabled, firefox70 disabled, firefox71 verified)
VERIFIED
FIXED
mozilla71
People
(Reporter: bytesized, Assigned: m_kato)
References
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce: 1) Open IRCCloud in Firefox Nightly on Windows 10 2) Switch to another tab 3) Wait to receive a ToastNotification from IRCCloud (when a user messages you, or when a channel you get notifications on gets a message) 4) Click the notification 5) Firefox switches to the IRCCloud tab 6) Start typing a reply Expected result: Typed reply text will display in the "send message" input box Actual result: Nothing displays in the "send message" input box because the Firefox window does not have focus.
Comment 1•6 years ago
|
||
[Tracking Requested - why for this release]: regression in usability of desktop notifications. This functionality was added in bug 853972 (Firefox 29) but was now regressed by bug 1155505. Please make sure to update the test at https://searchfox.org/mozilla-central/source/browser/base/content/test/alerts/browser_notification_tab_switching.js to cover the native notifications.
status-firefox63:
--- → unaffected
status-firefox64:
--- → affected
tracking-firefox64:
--- → ?
Flags: needinfo?(m_kato)
Keywords: regression
Assignee | ||
Comment 2•6 years ago
|
||
Toast Notification isn't turn on 64 release, so this isn't blocker for 64. And our unit test cannot use OS's toast because native toast requires AppId in shortcut file (it requires installer build that is *.exe)
Assignee: nobody → m_kato
Flags: needinfo?(m_kato)
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
I guess that clicking notification causes that application focus is switched. So we need set focus to Firefox again for windows. bug 853972's fix uses fm.setActiveWindow, but the latest code doesn't use it. So firefox cannot take window focus...
Assignee | ||
Comment 4•6 years ago
|
||
That change was bug 960997
Updated•6 years ago
|
tracking-firefox64:
? → ---
Updated•6 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Updated•6 years ago
|
status-firefox65:
--- → affected
Comment 5•5 years ago
|
||
Tracking this to make sure and follow up for 66 and possibly for 65.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
This feature is Nightly-only, so no need to track for 65.
Updated•5 years ago
|
status-firefox67:
--- → affected
tracking-firefox67:
--- → +
Updated•5 years ago
|
Assignee | ||
Comment 10•5 years ago
|
||
When clicking native toast on Windows 10, focus moves to another process,
So we have to set focus on Firefox process.
Comment 11•5 years ago
|
||
Pushed by m_kato@ga2.so-net.ne.jp: https://hg.mozilla.org/integration/autoland/rev/b296f51555f8 Set focus on Firefox since focus is moved to another process. r=aklotz
Comment 12•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Updated•5 years ago
|
status-firefox68:
--- → disabled
status-firefox69:
--- → disabled
status-firefox70:
--- → disabled
status-firefox-esr60:
--- → unaffected
status-firefox-esr68:
--- → disabled
Flags: qe-verify+
Comment 13•5 years ago
|
||
I have reproduced this issue in Nightly v71.0a1 from 2019-10-01 and verified it in Nightly v71.0a1 from 2019-10-08 in Windows 10.
Updated•10 months ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•