911566 - Desktop notifications created while owning a wake lock do not fire an onclick event

Status: RESOLVED WORKSFORME

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

Description

[Michael Diener]

Attachment: sample.zip - Sample webapp that reproduces the issue.

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36

Steps to reproduce:

When an alarm (via navigator.mozAlarms) is triggered, I acquire a wakelock (within I would normally download something) and then display a desktop notification (via navigator.mozNotification). The wakelock is released afterwards.


Actual results:

Alarm gets triggered, wakelock acquired, notification show, wakelock released. When clicking the notification, the onclick event is NOT triggered.


Expected results:

The onclick event should have been triggered.

Comment 1

[Michael Diener]

One more thing, this happens for B2G 1.0 and 1.1. I did not test 1.2 yet.

Comment 2

[Jason Smith [:jsmith]]

is this potentially a dupe of bug 910915 by any chance? Or is this different?

Comment 3

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

Could very well be. I'll take the bug. I've got the sample app downloaded and I'll try to test it with a new build.

Comment 4

[Jason Smith [:jsmith]]

Confirmed that the STR in this bug is no longer reproducing on today's Buri build - I'm seeing the onclick event firing in the logcat.

09-19 13:42:12.611: E/GeckoConsole(572): Content JS LOG at app://{4e5feef0-d64f-4484-b3b6-1e750edcbb20}/index.html:47 in notification.onclick: onclick

Comment 5

[Michael Diener]

Sounds good! Will this work in B2G 1.1 or 1.2?