onclick of notification not fired when outside of app

NEW
Unassigned

Status

()

6 years ago
2 years ago

People

(Reporter: marcuskrahl, Unassigned)

Tracking

20 Branch
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130307023931

Steps to reproduce:

1. Open Firefox for Android and go to https://developer.mozilla.org/samples/domref/desktopnotification.html
2. Click on the link to create a notification
3. Leave Firefox and switch to another app or the home screen
4. Click on the toast message of firefox

(Tested on a Samsung Galaxy S III with Android 4.1.2)


Actual results:

Firefox opens again but the relevant events (notification.onclick and notification.onclose) are not fired


Expected results:

Firefox opens again and notification.onclick and notification.onclose are fired.
(Reporter)

Updated

6 years ago
OS: Windows 7 → Android
Hardware: x86 → ARM
(Reporter)

Comment 1

6 years ago
The same thing occurs if I click the toast notification from another tab. Instead of switching to the corresponding tab and firing the events nothing happens
I see the intent in console on-tap; perhaps a problem with handleNotification?

I/ActivityManager(  519): START u0 {act=org.mozilla.gecko.ACTION_ALERT_CALLBACK dat=alert:/1050698552?name=desktop-notification:6&cookie=desktop-notification:6 flg=0x10000000 cmp=org.mozilla.fennec/.App bnds=[0,151][768,279]} from pid -1

another test

http://people.mozilla.org/~mwargers/tests/dom/moznotification.htm
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

5 years ago
blocking-b2g: --- → leo?

Comment 3

5 years ago
Not a critical regression in 1.1, bumping to koi? for backlog consideration in 1.2.
blocking-b2g: leo? → koi?
Unrelated to Firefox OS - pulling nom.
blocking-b2g: koi? → ---
You need to log in before you can comment on or make changes to this bug.