Closed
Bug 989478
Opened 11 years ago
Closed 11 years ago
[B2G][Notification API] Notifications with the same tag originating from different browser tabs will be replaced
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(b2g-v1.3 affected, b2g-v1.4 affected)
RESOLVED
INVALID
People
(Reporter: demerick, Unassigned)
References
()
Details
(Whiteboard: burirun1.4-2)
Attachments
(1 file)
|
213.33 KB,
text/plain
|
Details |
Description:
If a notification is fired with tag 'x' from one browser tab and another notification is fired with the same tag 'x' from a different tab, the notification on the phone will be replaced.
Repro Steps:
1) Update a Buri to BuildID: 20140326000201
2) Open Firefox from the home screen
3) Navigate to http://mozilla.github.io/qa-testcase-data/webapi/notifications/index.html
4) Tap 'Request' under 'Request Permission'
5) Create a notification with title 'a' and tag 'x' and tap 'Show Notification'
6) A notification should appear on the phone
7) Open another tab in the browser and navigate to http://mozilla.github.io/qa-testcase-data/webapi/notifications/index.html
8) Create a notification with title 'b' and tag 'x' and tap 'Show Notification'
Actual:
The first notification will be replaced by the second notification on the phone
Expected:
Both notifications should appear on the phone
1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140326000201
Gaia: 7e705dd4718d528974d99ac31866318d7e201152
Gecko: 4889124accfa
Version: 30.0a2
Firmware Version: v1.2-device.cfg
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9953/
See attached: logcat
Video URL: https://www.youtube.com/watch?v=Pkhpp1XkSDA
This issue reproduces on Buri 1.3 MOZ RIL.
1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140326004002
Gaia: 812838ad0fabf51fa14435af562ddac6d26fa936
Gecko: ba97efb0da4b
Version: 28.0
Firmware Version: v1.2-device.cfg
Notifications with the same tag originating from different browser tabs will replace each other.
Comment 2•11 years ago
|
||
This was tested incorrectly - the test case points out that the URL for step 7 uses a different URL than step 3.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•