New issue
Advanced search Search tips

Issue 822892 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Add metrics on credit card save prompt to distinguish between explicit denial and clicking outside of prompt

Project Member Reported by jsaul@google.com, Mar 16 2018

Issue description

Comment 1 by se...@chromium.org, May 1 2018

Status: Assigned (was: Untriaged)
Is this still relevant with the stickiness?

Comment 2 by jsaul@google.com, May 1 2018

Status: WontFix (was: Assigned)
Good question; not 100% sure.  However, given Nik's recent email it does seem like the prompt correctly differentiates explicit denials vs. "bubble was hidden when navigation happened", so I think these metrics are already in place as #c1 assumes.

Comment 3 by ma...@chromium.org, May 2 2018

Status: Assigned (was: WontFix)
Can you check manually through chrome://histograms that it works as expected? Then I'm fine with the WontFix.

Comment 4 by jsaul@google.com, May 17 2018

Cc: ma...@chromium.org se...@chromium.org
Thank you Mathieu; I forgot chrome://histograms existed, and it did point out a gap.

The bubble DOES correctly differentiate explicit denials vs. closing the bubble and navigating away.  However, it's not a matter of the stickiness, it's a matter of Harmony.  The [No thanks] button (when Harmony is off) is an explicit denial, while the top-right [X] close button (when Harmony is on) doesn't log anything of the sort and falls into the "bubble was hidden when navigation happened" funnel.  They also have slightly different behavior: [No thanks] hides the credit card icon in the omnibox entirely; [X] does not, just like the non-sticky version.

TL;DR: When Harmony is on, the [X] close button doesn't count as explicitly denying the prompt, just hiding it until tab navigation gets rid of it for good.

Sign in to add a comment