New issue
Advanced search Search tips

Issue 864194 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 6
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 864147



Sign in to add a comment

Add UKM for JS dialog dismissal reason

Project Member Reported by csharrison@chromium.org, Jul 16

Issue description

The dismissal reason can be used as a proxy for site abuse (e.g. if a user dismisses the dialog via closing the tab).
 
Components: -Blink>HTML>Dialog Blink>WindowDialog
Owner: yaoxia@chromium.org
The proposal for distinguishing based on "closing the tab" is a bit tough, as the JS dialog code doesn't know if its tab was closed when it's told to cancel the dialog.

The metric that I've used in the past in making arguments in Intents is DIALOG_BUTTON_CLICKED (that the user clicked a button and dismissed the dialog in that manner) vs everything else (which is either that the user went away from the page or killed it in some manner, or perhaps the page closed the dialog itself by popping another one). I would highly recommend using DIALOG_BUTTON_CLICKED vs everything else.
Status: Fixed (was: Untriaged)

Sign in to add a comment