Closed
Bug 1824743
Opened 2 years ago
Closed 2 years ago
A notification with both "surface": "notification" and "style": "NOTIFICATION" is not triggered if the one displayed by the branch before has not been dismissed
Categories
(Firefox for Android :: Experimentation and Telemetry, defect)
Tracking
()
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | affected |
| firefox113 | --- | unaffected |
People
(Reporter: mheres, Unassigned)
References
Details
Attachments
(1 file)
|
6.95 MB,
video/quicktime
|
Details |
[Affected Versions]:
- Firefox Beta 112 (local build set to Stage) (Build #2015940739), 4219b85b96+ GV: 112.0-20230313153916 AS: 97.2.0
[Affected Platforms]:
- Android 9 - Samsung Galaxy S8
- Android 13 - Samsung Galaxy Tab A8
[Prerequisites]:
- Have an experiment that contains multiple separate messages with both "surface": "notification" and "style": "NOTIFICATION" and with the same trigger, set in the same branch (e.g. this Stage experiment).
[Steps to reproduce]:
- Enroll in the experiment (observe that the appropriate branch is checked in Debug menu > Nimbus Experiments > name of experiment).
- Restart the app once.
- Change the time to 4 hours in the future.
- Confirm that the first message has been displayed in the notifications view.
- Change the time to 4 hours in the future again.
- Observe the notifications view.
[Expected result]:
- The second notification set up in the branch is displayed.
- The first notification remains displayed.
[Actual result]:
- The second notification set up in the branch is not displayed.
- The first notification remains displayed.
[Notes]:
- The second notification is displayed after the first one is dismissed or clicked.
- Attached is a recording of the issue.
Comment 1•2 years ago
•
|
||
This may be related to the Bug 1822899 - Off by one error in checking for expired messages.
The first message is displayed at 4. The display count is incremented to 1.
At the second time of doing work (step 6), the first message comes up again, blocking the second message from being displayed.
| Reporter | ||
Comment 2•2 years ago
|
||
It looks likely that it is . The issue is not reproducible on Firefox Nightly 113.0a1 (Build #2015941859), c56db2d798 GV: 113.0a1-20230329095653 AS: 97.3.0, which should contain the fix to Bug 1822899.
| Reporter | ||
Updated•2 years ago
|
status-firefox113:
--- → unaffected
Comment 3•2 years ago
|
||
This is fixed in main for v113.
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•2 years ago
|
||
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•