Closed
Bug 1877178
Opened 2 years ago
Closed 1 year ago
No dismiss telemetry is registered if any of the MailTo infobar is dismissed by clicking the "X" button
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1880644
People
(Reporter: cmuntean, Unassigned)
References
Details
Attachments
(1 file)
|
1.39 MB,
video/mp4
|
Details |
[Affected versions]:
- Firefox Release 122.0 (Build ID: 20240118164516)
- Firefox Beta 123.0b3 (Build ID: 20240126091653)
- Firefox Nightly 124.0a1 (Build ID:20240128212206)
[Affected Platforms]:
- macOS 13.1
- Windows 10 x64
- Ubuntu 20.04
[Prerequisites]:
- Firefox is NOT set as the default OS mailto handler (Windows Settings -> Choose the default app by protocol -> MAILTO:Thunderbird)
- The "Always ask" action is set for the "mailto" content type in about:preferences -> Applications.
- Have a new profile with the following prefs set:
browser.mailto.dualPrompt set to true
browser.mailto.dualPrompt.os set to true
browser.mailto.prompt.os set to true
[Steps to reproduce]:
- Open the browser with the settings described in prerequisites.
- Navigate to about:glean, set a tag and select the "metrics" type.
- Navigate to the following test website: https://snappymail.eu/demo/.
- Click the "SIGN IN" button.
- Click the "X" button for both infobars displayed.
- Navigate back to about:glean and click the "Apply setting and submit ping".
- Navigate to https://debug-ping-preview.firebaseapp.com/pings/, choose your tag set in Step 2.
- Verify the latest "metrics" ping.
[Expected result]:
- The "protocolhandler.mailto.prompt_clicked" is registered and has the "dismiss_os_default": 1" and "dismiss_local_default": 1 values.
[Actual result]:
- The "protocolhandler.mailto.prompt_clicked" is NOT registered.
[Notes]:
- The telemetry is correctly registered if the "Not now" button is clicked.
- Attached a screen recording of the issue.
Comment 2•1 year ago
|
||
I am going to mark this bug as a duplicate (even though it exists longer), because Bug 1880644 is more generic (and not only about the 'x' button)
You need to log in
before you can comment on or make changes to this bug.
Description
•