[B2G][Flame][2.0][Web Notifications API] "onclose fired" shown on the logcat when notifications are cleared.

RESOLVED INVALID

Status

RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: ychung, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Bug Flags:
in-moztrap +

Firefox Tracking Flags

(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

Details

(Whiteboard: [2.0-flame-test-run-3], URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8465003 [details]
logcat_20140730_OncloseShown.txt

Description:
When the user clears all notifications generated by the notifications API, logcat displays onclose fire.

Repro Steps:
1) Updated Flame to Build ID: 20140730000206.
2) Open Browser, and go to http://mozilla.github.io/qa-testcase-data/webapi/notifications/index.html.
3) Select "Request" under "Request Permission".
4) Under "Show Notification", create 3 different notifications.
5) Pull down the notification overlay, and select "Clear all".

Actual:
"in notification.onclose: onclose fired on title:[...]" is displayed for each notification on logcat.

Expected:
onclose fire is not displayed on logcat.

Flame 2.0 (319mb)

Environmental Variables:
Device: Flame 2.0
Build ID: 20140730000206
Gaia: 2e85678de2c8e13e585288d4cec7d6673cee17ee
Gecko: 6e37ecf873da
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Repro Frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9946/
See attached: logcat
(Reporter)

Comment 1

4 years ago
This issue also reproduces on Flame 2.0(512mb), Flame 2.1(319mb), Flame 1.4(319mb), Buri 2.0, Buri 2.1, Buri 1.4:

Flame 2.0(512mb)

Environmental Variables:
Device: Flame 2.0
Build ID: 20140730000206
Gaia: 2e85678de2c8e13e585288d4cec7d6673cee17ee
Gecko: 6e37ecf873da
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 2.1(319mb)

Environmental Variables:
Device: Flame Master
Build ID: 20140730040205
Gaia: 25e998814ba89f30fe44cd2fdfbb44d160a04641
Gecko: 55c4d770f88b
Version: 34.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 1.4(319mb)

Environmental Variables:
Device: Flame 1.4
Build ID: 20140730063005
Gaia: 142953262d2cb031e3db217206edc3507580b0df
Gecko: 17de7b9d035c
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140730063007
Gaia: 2e85678de2c8e13e585288d4cec7d6673cee17ee
Gecko: 2b6108c94b2e
Version: 32.0 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Buri 2.1

Environmental Variables:
Device: Buri Master
Build ID: 20140730073003
Gaia: 25e998814ba89f30fe44cd2fdfbb44d160a04641
Gecko: 08c23f12a43e
Version: 34.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Buri 1.4

Environmental Variables:
Device: Buri 1.4
Build ID: 20140730063005
Gaia: 142953262d2cb031e3db217206edc3507580b0df
Gecko: 17de7b9d035c
Version: 30.0 (1.4)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Onclose fire is displayed for each notification on logcat.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
This is done on purpose. The clear all button manually closes (and fires the associated event, for each notification). I think we have an invalid test case.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
Kevin - Can you update the test case here to say that onclose should fire?
Flags: in-moztrap?(ktucker)
Test case has been updated.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(ktucker)
Flags: in-moztrap+

Comment 5

4 years ago
This test case is still valid. Kevin has previously updated the test case of 7/31/14
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Flags: in-moztrap?
Flags: in-moztrap+

Updated

4 years ago
Flags: in-moztrap? → in-moztrap?(jthomas)
Test case has been updated to state that "onclose should fire":

https://moztrap.mozilla.org/manage/case/9946/
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(jthomas)
Flags: in-moztrap+
You need to log in before you can comment on or make changes to this bug.