Open Bug 1603762 Opened 3 years ago Updated 3 years ago

Notification request from is suppressed


(Core :: DOM: Push Notifications, defect, P2)




Tracking Status
firefox73 - fix-optional
firefox74 --- affected


(Reporter: ehsan.akhgari, Unassigned)


(Blocks 1 open bug)


If you visit in a profile where it doesn't have the notification permission already it will choose a random time to ask you to grant it notification access. The notification access grant isn't requested with user gesture so we don't show the prompt any more and only show the icon in the URL bar.

When this happened to me the first time, it took me a couple of days to notice it and I missed a meeting as a result.

Peter, would you mind reaching out to our Google contacts about this issue please? Thanks!

Flags: needinfo?(stpeter)
Flags: needinfo?(jhofmann)

My idea to solve this would be that we could introduce a time limit after which sites that already had user interaction once will be able to visibly prompt again. If we make that sufficiently large I don't think we're in a bad place from the annoyance perspective. Felix, could you do me the favor and take another quick look at our data to figure out if there's an amount of time after which "accept" rates are significantly increasing? If such a number exists, we could use it here.

Flags: needinfo?(jhofmann) → needinfo?(flawrence)

I'm a bit slammed right now; will try to get to it next week (before PTO and all hands and more PTO) but I can't promise it... If it's really important that it gets done then please file a DS ticket.

Priority: -- → P2
Flags: needinfo?(flawrence)
Flags: needinfo?(jstutte)

Hi Felix, are you still slammed or can you get to this?

Flags: needinfo?(jstutte) → needinfo?(flawrence)

I'm still pretty slammed, and I've moved teams (out of product DS, now focussing on metrics and segments), so I'm probably not the right person to do this. I'd recommend filing a JIRA ticket and likely another DS will take it on.

In the ticket it's probably worth including the context to give the next DS a leg up: the report and the databricks notebook that generated the report. I'll also happily chat to the other DS to help them out. But I don't think I can justify giving a day or two to this right now (e.g. all the spark queries need to be rewritten in SQL) without this going through triage.

Flags: needinfo?(flawrence)

I just sent a note about this issue to the coordination list.

Flags: needinfo?(stpeter)
Severity: normal → S3
Flags: needinfo?(jstutte)

(In reply to Peter Saint-Andre [:stpeter] from comment #6)

I just sent a note about this issue to the coordination list.

Did you ever receive a response? Thank you!

Flags: needinfo?(jstutte) → needinfo?(stpeter)

Our Google friends filed an internal issue and I just pinged them for a status.

Flags: needinfo?(stpeter)
You need to log in before you can comment on or make changes to this bug.