925160 - [B2G][Notifications API] Logcat does not show onshow/onerror

Status: RESOLVED DUPLICATE of bug 920302

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[Deepa Subramanian]

Attachment: notification logcat.txt

I/GeckoDump(139): XXX FIXME : Got a mozContentEvent: desktop-notification-show

Description:
User is unable to see "Onshow /Onerror/Onclick/Onclose" on the logcat for notifications.

Pre-requisite: Have ADB logcat running.

Repro Steps:
1) Updated Buri Build ID: 20131009004001.
2) Go to http://mozilla.github.io/qa-testcase data/webapi/notifications/index.html.
3) Tap on "Request permission".
4) Upon permission granted, have title alone as "Test Title".
5) Tap "Show Notification".
6) Look for "Onshow firing" in the logcat.

Actual:
Logcat DOES NOT mention "Onshow" upon tapping "Show notification" button.

Expected:
Logcat mentions "Onshow" upon tapping "Show notification" button.

Notes: This fails multiple test cases. Please see the tinyURL provided. 

Environmental Variables
Build ID: 20131009004001
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/e5edb484e2a9
Gaia: 672c47bf94b69a329e0aacb9228a6aa16ade6226
Platform Version: 26.0a2

Repro frequency: 100%
Test Suite Name: (Notification
UCID: System0
Link to failed test case: http://goo.gl/P8wOQC
See attached: logcat

Comment 1

[Deepa Subramanian]

While testing on v1.1 of today's build found that the buttons(Install, Request, Show Notification, Close) on http://mozilla.github.io/qa-testcase-data/webapi/notifications/index.html where unresponsive to test it this particular defect.

Environmental Variables:

LEO Build ID: 20131009041203
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/c630289d6388
Gaia: 53e2a70d85fb3748d0768218a5efffe5806073f0
Platform Version: 18.1
RIL Version: 01.01.00.019.238

Comment 2

[Jason Smith [:jsmith]]

Note - this is a bug in a 1.2 feature, so this won't be reproducible in 1.1.

Comment 3

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

I've got integration tests for this in Bug 922382 that were giving me similar results.

Comment 4

[Preeti Raghunath(:Preeti)]

Jason

Is this a 1.2 broken feature?

Comment 5

[Jason Smith [:jsmith]]

Yes. This means that the event handlers specified in the bug are not firing for the Web Notifications API, which breaks two System FE user stories at a basic level.

Comment 6

[Jason Smith [:jsmith]]

blocking+ - event handlers need to work for the notifications api

Comment 7

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Run with v1.2 on Nexus 4. UI Tests, which show alerts on event firing versus relying on logcat, work fine. Desktop integration tests also confirm events are working. 

Might want to change this test to use a mechanism that can be seen in the OS?

Comment 8

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

WFM was for app perms, not browser. Even so, most likely a dupe of Bug 920302, since both would happen due to notification messages not relaying correctly in browser context. Updating to reflect.