638568 - Remove "Not Now" menuitem from popup notifications

Status: RESOLVED DUPLICATE of bug 1282768

(Toolkit Graveyard :: Notifications and Alerts, defect)

Description

[:Margaret Leibovic]

Because we ended up implementing bug 615315, I think we should get rid of the "Not Now" menuitem in popup notifications.

If we get rid of that menuitem, we should WONTFIX bug 615441.

Comment 1

[:Margaret Leibovic]

Attachment: patch

This is basically a backout of the patch from bug 615318, but some things needed to stay in for the close button to work (bug 615315).

Comment 2

[Alex Faaborg [:faaborg] (Firefox UX)]

Comment on attachment 520325 [details] [diff] [review]
patch

The redundancy built in here is kind of controversial, but the objective was to allow the user to view every available choice in a single organized list, so that they didn't have to store previously viewed choices in memory (main action, close button) as they simultaneously consider the alternate commands.  So in conjunction with the work proposed over in bug 615441, I'm in favor of keeping the "not now" command in this list.

Comment 3

[:Margaret Leibovic]

I understand that design, and I agree that if we keep the "Not Now" menuitem, we should also have a redundant main command.

However, I've seen users click on the "Not Now" menuitem, and it's a painfully slow interaction. I feel like users are more likely to learn that they can click outside to close the notification if they don't have the "Not Now" option, but they will still have the close button in case they can't figure out that click outside to close interaction.

I understand that once they already open the dropdown menu, it is probably slower to hit the close button than to choose "Not Now", but for single-action notifications, I feel like we're wasting users' time if they click on the dropdown out of curiosity, only to see that the only additional option is "Not Now".

I'm also cc'ing Limi because we were just talking about this now, and he agrees with these points.

Comment 4

[Alex Faaborg [:faaborg] (Firefox UX)]

>I feel like we're wasting users' time if they click on the
>dropdown out of curiosity, only to see that the only additional option is "Not
>Now".

Yeah, I totally agree with that.  Regardless of bug 615441, there shouldn't be a drop down if there are no alternate commands.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

Having the not-now option there can be harmful even for notifications that have multiple secondary actions - users who are just discovering this new UI could conclude (based on its presence) that it's the only way to dismiss the notification. I suppose now that we've already shipped it we kind of have that problem regardless...

Comment 6

[Matthew N. [:MattN]]

(In reply to Alex Faaborg [:faaborg] (Firefox UX) from comment #4)
> >(In reply to Margaret Leibovic [:margaret] from comment #3)
> >I feel like we're wasting users' time if they click on the
> >dropdown out of curiosity, only to see that the only additional option is "Not
> >Now".
> 
> Yeah, I totally agree with that.  Regardless of bug 615441, there shouldn't
> be a drop down if there are no alternate commands.

If I implement this (not adding "Not now" if there are no secondary actions), will it be accepted? It seems like there is agreement on this portion.

Comment 7

[:Margaret Leibovic]

(In reply to Matthew N. [:MattN] from comment #6)
> (In reply to Alex Faaborg [:faaborg] (Firefox UX) from comment #4)
> > >(In reply to Margaret Leibovic [:margaret] from comment #3)
> > >I feel like we're wasting users' time if they click on the
> > >dropdown out of curiosity, only to see that the only additional option is "Not
> > >Now".
> > 
> > Yeah, I totally agree with that.  Regardless of bug 615441, there shouldn't
> > be a drop down if there are no alternate commands.
> 
> If I implement this (not adding "Not now" if there are no secondary
> actions), will it be accepted? It seems like there is agreement on this
> portion.

I like this idea. I'm probably not the person who needs to okay this, though :)

Comment 8

[:Gavin Sharp [email: [e-mail]]]

(In reply to Matthew N. [:MattN] from comment #6)
> If I implement this (not adding "Not now" if there are no secondary
> actions), will it be accepted? It seems like there is agreement on this
> portion.

Yes please!

Comment 9

[Matthew N. [:MattN]]

Bulk move to Toolkit::Notifications and Alerts

Filter on notifications-and-alerts-component.

Comment 10

[Matthew N. [:MattN]]

Not now will be removed from permission prompts as part of bug 1188147's dependencies.

Comment 11

[Panos Astithas (he/him) [:past] (please ni?)]

I am removing Not Now in bug 1282768.