Closed
Bug 1280202
Opened 8 years ago
Closed 2 years ago
Provide "Block" option on Push Notifications permission doorhanger
Categories
(Core :: DOM: Push Subscriptions, enhancement, P3)
Core
DOM: Push Subscriptions
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: djc, Unassigned)
References
Details
(Keywords: ux-control)
When loading a site that has Web Push notifications, Firefox shows a doorhanger that offers options to enable push notifications. If I have not granted the site any special permissions, the doorhanger provides two options: - Always Receive Notifications - Not Now This means that, if I don't want to receive Web Push notifications from this site, I have to click "Not Now" every time, or go hunting for a way to block them. Blocking them in this case is way hidden in the Permissions Tab of the Page Info dialog, which is completely non-obvious even for me as a fairly sophisticated user.
Comment 1•8 years ago
|
||
We're redesigning the doorhanger. I think these are the mockups: https://mozilla.invisionapp.com/share/PC3Y0QSRK#/screens/96290117 . What do you think?
Flags: needinfo?(dirkjan)
Reporter | ||
Comment 2•8 years ago
|
||
I like how the "allow" vs "remember" decisions are orthogonal, that seems like a bit improvement. I also like the new permissions over view in the control center widget, and how it can be manipulated. Personally, I think the (i) icon for the control center sucks a little bit since to me it implies something passive (where I can see some information), not something that gives me options to change.
Flags: needinfo?(dirkjan)
Comment 3•8 years ago
|
||
Aislinn is probably interested in your thoughts here, Dirkjan.
Flags: needinfo?(agrigas)
Comment 4•8 years ago
|
||
(In reply to Dirkjan Ochtman (:djc) from comment #0) > When loading a site that has Web Push notifications, Firefox shows a > doorhanger that offers options to enable push notifications. If I have not > granted the site any special permissions, the doorhanger provides two > options: > > - Always Receive Notifications > - Not Now > > This means that, if I don't want to receive Web Push notifications from this > site, I have to click "Not Now" every time, or go hunting for a way to block > them. Blocking them in this case is way hidden in the Permissions Tab of the > Page Info dialog, which is completely non-obvious even for me as a fairly > sophisticated user. I agree - I think notification options should be consistent with the other permissions types and have a block/don't allow and a 'allow' - the one issue is that the checkbox to remember choice, most people said should be checked by default for this case so that users that want to allow notifications don't have to keep clicking allow. We kind of can only optimize for easy permanent allowing or easy temporary blocking and not both without needing a new UI model. Given that, we're assuming most people want the richer service experience that notifications provide and therefore would have a default of always allow (checkbox selected for the user). This supports the 'block always' case but drops support for the not now case as it is the most effort to unselect the check box.
Flags: needinfo?(agrigas)
Comment 5•8 years ago
|
||
Also worth noting that the Push team is looking into experiments which would prevent sites (which have never been visited before) from asking for a permission on first load. If successful this could prevent a lot of the annoying permission requesting from various sites.
Reporter | ||
Comment 6•8 years ago
|
||
I think enabling the checkbox by default makes sense, as that means that in general I only to chose once per site. Is there telemetry on what people are doing in general? I would guess that any user will only enable push notifications on a quite small number of sites.
Updated•4 years ago
|
Type: defect → enhancement
Comment 7•2 years ago
|
||
It now says Allow / Always Block.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•