New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users

Issue metadata

Status: Fixed
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 542232
issue 571056

Sign in to add a comment

Issue 530697: Add finch control for auto-dismiss timeout of notifications

Reported by, Sep 11 2015 Project Member

Issue description

We should add a finch control to the auto-dismiss timeout of notifications so we can adjust it without a 6-12 week delay.

Comment 1 by, Sep 11 2015


The current default is 8 seconds. Justin, do you remember how this was chosen? Experiments done by a partner seem to indicate that 15-20s has the best CTR.

Comment 2 by, Sep 11 2015

Not sure if there was any actual data for this choice, beyond comparisons to other existing notification systems at the time.  Note that priority=1 notifications have a timeout of something like 21 seconds, so that could also be controlled by finch.

Comment 3 by, Sep 11 2015

Also I am happy to reconfigure the defaults based on data from partners or otherwise.

Comment 4 by, Sep 11 2015

Status: Available
One thing I particularly care about is predictability - if all notifications stay on-screen for either 8 or 25 seconds, *except* for this one kind of notification, it's just going to be annoying for users.

For this reason I think doing an experiment makes sense. I think the most useful metric for A/B testing are the number of manually dismissed notifications; clicks will naturally rise the longer a notification is on screen.

Comment 5 by, Sep 29 2015

Labels: M-48
Status: Assigned
We'll increase the timeout for M47, but really want to run our own experiments in M48.

Comment 7 by, Oct 7 2015

Labels: Merge-Request-47
Requesting merge of to m47. It's a safe patch, and will avoid developers having to implement hackish workarounds that will break in future version of Chrome (risking compatibility issues).

Comment 8 by, Oct 8 2015

Labels: -Merge-Request-47 Merge-Approved-47 Hotlist-Merge-Approved
Approved for M47 (branch: 2526)

Comment 9 by, Oct 9 2015

Project Member

Comment 10 by, Oct 9 2015

Project Member

Comment 11 by, Oct 12 2015

Blockedon: chromium:542232

Comment 12 by, Oct 20 2015

Project Member
The following revision refers to this bug:

commit f272cc7c00097e01454be7f7f370516b52989b7f
Author: johnme <>
Date: Tue Oct 20 13:51:40 2015

Add use counter for user closing a persistent notification.

Adds a Notifications.Persistent.ClosedByUser use counter.

This is a follow-up to f52d070a3cae53f27cf9490428770b64e73c16d0
( which added a
Notifications.Persistent.Closed use counter that included both closing
by user and by system.

BUG= 530697 

Review URL:

Cr-Commit-Position: refs/heads/master@{#355050}


Comment 13 by, Jan 12 2016

Blockedon: chromium:571056
Labels: -Pri-2 -M-48 Pri-3
Owner: ----
Status: Available
Deprioritizing Finch experiment as 20 seconds seems to be working well so far, and efforts like  issue 571056  might make it redundant.

Comment 14 by, Jan 12 2016

Is that statement based on (the lack of) user reports? Do we have data?

If we feel that this is an appropriate amount of time, let's make sure that we change extensions (kAutocloseHighPriorityDelaySeconds) to match this and close this issue.

Comment 15 by, Feb 4 2016

So lets say someone walks away from their computer then comes back to no notifications? Do you see the problem here? Our chat application's user experience is suffering due to 20 second timeout on notifications. Thoughts?

Comment 16 by, Apr 21 2016

Project Member
For more details visit - Your friendly Sheriffbot

Comment 17 by, Dec 15 2016


Comment 18 by, Jul 4 2017

Status: Assigned (was: Available)
High-priority and Web notifications should just use the same value. CL uploaded:

Comment 19 by, Jul 7 2017

Project Member
The following revision refers to this bug:

commit fd9298e768838d6f0adfffcbd5733fa627edebb0
Author: Peter Beverloo <>
Date: Fri Jul 07 17:48:56 2017

Align on-screen time of high priority and Web notifications

These used to remain on-screen for respectively 25 and 20 seconds, the
difference in which is a bit silly. Let's both keep them on-screen for
25 seconds.

BUG= 530697 

Change-Id: I082ecfc69ec69e600818b113b02e161e058a830f
Commit-Queue: Peter Beverloo <>
Reviewed-by: John Mellor <>
Reviewed-by: Yoshiki Iguchi <>
Cr-Commit-Position: refs/heads/master@{#484976}

Comment 20 by, Jul 11 2017

Status: Fixed (was: Assigned)

Sign in to add a comment