Record additional event telemetry on user interaction with permission prompts
Categories
(Firefox :: Site Identity, enhancement, P1)
Tracking
()
People
(Reporter: johannh, Assigned: johannh)
References
Details
Attachments
(6 files)
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
3.71 KB,
text/plain
|
chutten
:
data-review+
|
Details |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
For limited field (shield) studies we would like to have precise event telemetry about different metric when a user interacts with permission prompts.
This could be used to build heuristics to automatically reject permission prompts in the future.
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
Almost none of the prompts that we are currently showing still get dismissed, which messes up our
measurements in this probe. Most of them are persistent now, which means that we should record when
they get removed instead of dismissed to receive meaningful data. This patch does that.
| Assignee | ||
Comment 5•6 years ago
|
||
| Assignee | ||
Comment 6•6 years ago
|
||
This is still lacking basic tests (we could test an endless combination of things but I'd like to have at least some basic assertions), and I will file the data review request after we're done with our conversation with legal on approving this study.
Thanks!
| Assignee | ||
Comment 7•6 years ago
|
||
Updated•6 years ago
|
Comment 8•6 years ago
|
||
| Assignee | ||
Comment 9•6 years ago
|
||
| Assignee | ||
Comment 10•6 years ago
|
||
| Assignee | ||
Comment 11•6 years ago
|
||
| Assignee | ||
Comment 12•6 years ago
|
||
| Assignee | ||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/565279f28841
https://hg.mozilla.org/mozilla-central/rev/c4beb7256d16
https://hg.mozilla.org/mozilla-central/rev/8c6ec5c528ff
https://hg.mozilla.org/mozilla-central/rev/19b40bd2e67f
https://hg.mozilla.org/mozilla-central/rev/4b317b418c14
| Assignee | ||
Comment 16•6 years ago
|
||
Comment on attachment 9057302 [details]
Bug 1536454 - Part 1 - Add userHadInteractedWithDocument and documentDOMContentLoadedTimestamp attributes to nsIContentPermissionPrompt. r=Ehsan
Beta/Release Uplift Approval Request
- User impact if declined: None, this is a preffed-off telemetry collection that will only be used for a study we are planning to run in Release 67 (we already announced this to rel-man), see https://blog.nightly.mozilla.org/2019/04/01/reducing-notification-permission-prompt-spam-in-firefox/
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: We hope to get separate testing for the Telemetry itself (besides the automated tests), but it would be nice to get a sanity check that permission prompts are still working (see https://permission.site/) on Beta after uplift.
- List of other uplifts needed: To avoid merge pains we would need bug 1508961 uplifted, too. :/
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The main risk with this patch is it's size, and the fact that it depends on bug 1508961. Otherwise, this is entirely preffed-off, has extensive test coverage and should have no user facing consequences even if enabled.
- String changes made/needed: None
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 17•6 years ago
|
||
List of other uplifts needed: To avoid merge pains we would need bug 1508961 uplifted, too. :/
I just realized we need bug 1524619 as well.
Hi Johann, do we have new telemetry data coming in from Nightly based on commits in comment 15? I am always a bit wary of uplifting telemetry related changes in Beta until we know we are seeing some of the data from Nightly users.
Updated•6 years ago
|
| Assignee | ||
Comment 19•6 years ago
|
||
(In reply to Ritu Kothari (:ritu) from comment #18)
Hi Johann, do we have new telemetry data coming in from Nightly based on commits in comment 15? I am always a bit wary of uplifting telemetry related changes in Beta until we know we are seeing some of the data from Nightly users.
Hi Ritu, that's a very valid concern. We initially turned this off in Nightly by default, because this was only intended for the experiment. But seeing that we made a last minute decision to remove the C3 data collection after all, it should be fine to enable in Nightly. I'll file a bug for it.
However, that still means we won't have Telemetry data coming in for another couple of days. I would still like to get this onto Beta as early as possible. My main concern is about breaking things by merging all these patches into Beta, so I'd prefer to be optimistic about the telemetry here. It has good test coverage and I just tried it myself on Nightly and things show up correctly in about:telemetry.
Maybe instead of waiting on the data, the QA team can try to verify this on Nightly first?
STR are:
- Enable
permissions.eventTelemetry.enabledin about:config - Go to https://permission.site, click on "Notifications" or "Geo"
- Visit
about:telemetry-> Events - You should see an entry for
security.ui.permissionpromptwith theshowmethod and the correct type (geo or notifications) - Respond to the prompt or leave the site
- Refresh
about:telemetry - You should see an entry for
security.ui.permissionpromptwith the method corresponding to what you did (allow, deny, leave)
Might also be nice to test this:
- Enable
permissions.eventTelemetry.enabledin about:config - Disable
dom.webnotifications.requireuserinteraction - Go to https://www.cnet.com/, notice a prompt is shown
- You should see an entry for
security.ui.permissionpromptwith theshowmethod and the correct type (geo or notifications) - Respond to the prompt or leave the site
- Refresh
about:telemetry - You should see an entry for
security.ui.permissionpromptwith the method corresponding to what you did (allow, deny, leave)
Brindusa, are you the right person to tackle this? :)
Thank you!
Comment 20•6 years ago
|
||
Hi, I have retested this issue on our latest Version of Nightly and I couldn't find any issues, everything works according to plan.
Event>Telemetry shows the Correct Leave, Allow, Deny or Never messages according to my selection from the https://www.cnet.com/ website prompt.
Updated•6 years ago
|
Comment 21•6 years ago
|
||
Forgot to mention that this issue was tested on all Operating Systems using Johann's steps from Comment 19. Thanks.
| Assignee | ||
Comment 22•6 years ago
|
||
Awesome, thanks for the quick confirmation ⚡️
Updated•6 years ago
|
Comment 23•6 years ago
|
||
Comment on attachment 9057302 [details]
Bug 1536454 - Part 1 - Add userHadInteractedWithDocument and documentDOMContentLoadedTimestamp attributes to nsIContentPermissionPrompt. r=Ehsan
P1, preffed-off by default and QA verified on nightly. uplift approved for 67 beta14. I reset the qe-verify+ keyword as I would like this uplift to be tested manually again by QA once it is on beta. Thanks.
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 24•6 years ago
|
||
| bugherder uplift | ||
https://hg.mozilla.org/releases/mozilla-beta/rev/f71a18e81a69
https://hg.mozilla.org/releases/mozilla-beta/rev/fbe79e8981f7
https://hg.mozilla.org/releases/mozilla-beta/rev/fe7f1569e8d6
https://hg.mozilla.org/releases/mozilla-beta/rev/759d4a9a8970
https://hg.mozilla.org/releases/mozilla-beta/rev/156dcfca7e31
Comment 25•6 years ago
|
||
Hi, I have retested this issue on all Operating systems with our latest Beta 67.0b14 and I can confirm this issue Verified as Fixed according to the steps from Comment 19.
I will mark this issue accordingly.
Description
•