Notification request from calendar.google.com is suppressed
Categories
(Core :: DOM: Push Subscriptions, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox73 | - | fix-optional |
firefox74 | --- | affected |
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
If you visit calendar.google.com 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.
Reporter | ||
Comment 1•5 years ago
|
||
Peter, would you mind reaching out to our Google contacts about this issue please? Thanks!
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
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.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
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.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•4 years ago
|
||
Hi Felix, are you still slammed or can you get to this?
Comment 5•4 years ago
|
||
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.
Comment 6•4 years ago
|
||
I just sent a note about this issue to the coordination list.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 7•4 years ago
|
||
(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!
Comment 8•4 years ago
|
||
Our Google friends filed an internal issue and I just pinged them for a status.
Comment 9•1 year ago
•
|
||
I'll close this as inactive for now, as I think Google Calendar now requests permission immediately after user interaction, not just randomly (assuming that you enabled desktop notification in account settings at all). But feel free to reopen if there's still a significant problem.
Description
•