1399957 - Onboarding snippets should have a 1-hour delay if they are closed via the "x" on the snippet

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, enhancement, P3)

Description

[Aaron Benson]

After clicking the "x" on an onboarding snippet, we should not show any new snippet for 1 hour. The Firefox logo in the top left should behave as already designed by showing either the Logo + message bubble, Logo + dot, or watermark Logo.

Comment 1

[Aaron Benson]

Some more rationale for this:

We're working to make snippets as unobtrusive as possible. To that end, if you close a snippet, there is a 1-hour gap before you would see the next one. One hour should provide enough time to be "out of sight, out of mind". The same behavior should exist for onboarding snippets since they are essentially the same thing.

Comment 2

[[e-mail]]

Hi Verdi, could you help confirm this is the behavior you want?

Please also notice this is the new feature request after the merge day...

Comment 3

[Verdi [:verdi] Best to slack me]

(In reply to Fred Lin [:gasolin] from comment #2)
> Hi Verdi, could you help confirm this is the behavior you want?
> 
> Please also notice this is the new feature request after the merge day...

Yes we agreed over slack with Peter on this today.

Comment 4

[Fischer [:Fischer]]

The bug 1393489 wants to let AS control onboarding notification so we may need to think how to approach these 2 requests without behavior conflicts.
(In reply to Aaron Benson from comment #0)
> After clicking the "x" on an onboarding snippet, we should not show any new
> snippet for 1 hour. The Firefox logo in the top left should behave as
> already designed by showing either the Logo + message bubble, Logo + dot, or
> watermark Logo.
If the top-left Firefox logo button should behave as already designed, I would expect during that 1-hr mute session the blue dot would show without mouse hovering and the speech bubble would show on mouse hovering, right?

Comment 5

[Aaron Benson]

That's right.

Comment 6

[Francis Lee [:frlee]]

per discussion with Aaron and all onboarding members, this will be handled in post-57 (ex. 58)