When pressing the ‘Make default’ button multiple times there is a delay in displaying the notification.
Categories
(Firefox :: Shell Integration, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox126 | --- | affected |
People
(Reporter: mchiorean, Unassigned)
References
Details
Attachments
(2 files)
Win11.gif
Found in
- version: 126.0a1
Affected versions
- version1: 127.0a1
Tested platforms
- Affected platforms: Windows 10/11
- Unaffected platforms: Mac, Ubuntu.
Preconditions
- Have Firefox installed
Steps to reproduce
- Go to about:preferences and press on Make default button.
- Repeat step1 multiple times.
Expected result
- ‘Finish making Nightly your default’ notification messages should be displayed each time.
Actual result
- ‘Finish making Nightly your default’ notification messages are being displayed with a considerable delay, and sometimes not displayed at all.
Regression range
- Not a regression as this was recently added.
Additional notes
- Attached there are 2 screenshots from Win10 and Win11, which are slightly different.
|
Reporter | |
Comment 1•1 year ago
|
||
|
|
Reporter | |
Comment 2•1 year ago
|
||
|
||
Comment 3•1 year ago
|
||
:pdahiya This probably relates to what you warned me about with frequency capping messages? Thoughts on how this should be handled differently (does it need to be handled differently)?
I'm kind of surprised this seems to be some difference between Windows 10 and 11, that might be an OS detail for applications spamming notifications that stay on screen.
|
||
Comment 4•1 year ago
|
||
@nrishel Expected Result in description of this bug expects ‘Finish making Nightly your default’ notification messages should be displayed each time.
My feedback in patch was if there is product need of hiding Toast Notification message after being shown certain number of times using custom frequency cap e.g. maximum twice in a day or an hour to avoid multiple click spam seen in win10 experience and yes unclear on win11 experience difference it does looks like OS level change.
|
|
||
Comment 5•1 year ago
|
||
Nothing stood out in the logs when testing this. At a glance it looks like Windows 10 has some kind of race condition wrt notifications when spammed. Windows 11 by contrast always kicks a notification to the action center if it is a persistent notification still visible when we re-issue the same notification ID, so the effect is that every other notification not moved to the action center via user interaction is moved into the action center when re-sent.
It might be worth creating a minimal program to verify the issue exists outside of Firefox, then sending it off to Microsoft. In the meantime, I don't think this is a critical issue to resolve.
Description
•