Open
Bug 1864182
Opened 2 years ago
Updated 5 months ago
[Experiment] The “CLICK_BUTTON“ and “SELECT_CHECKBOX” telemetry pings are generated for each click action if the “Next” button from the Survey Screen is clicked multiple times
Categories
(Firefox :: Messaging System, defect, P2)
Tracking
()
NEW
People
(Reporter: cfat, Unassigned)
References
(Blocks 1 open bug)
Details
[Affected versions]:
- Firefox Release 119.0.1 - Build ID: 20231106151204
- Firefox Beta 120.0b1 - Build ID: 20231023135443
[Affected Platforms]:
- Windows 10 x64
- Windows 11 x64
[Prerequisites]:
- Have a new Firefox profile.
- Firefox is not set as the default browser.
- Have the following prefs in the "about:config" page:
nimbus.debugpref set totrue;
browser.ping-centre.logpref set totrue; - Have the "Browser Console" opened.
[Steps to reproduce]:
- Open the browser with the profile from the prerequisites.
- Navigate to
about:studies?optin_slug=ask-new-profiles-if-they-are-a-new-or-existing-firefox-user-fx119&optin_branch=treatment-b&optin_collection=nimbus-preview. - Restart the browser.
- Navigate to “about:welcome”.
- Click any of the radio buttons from the Survey screen.
- Click the “Next” button multiple times.
- Focus the "Browser Console" and observe the experiment related telemetry pings.
[Expected result]:
- The “CLICK_BUTTON“ and “SELECT_CHECKBOX” telemetry pings are generated once.
[Actual result]:
- A telemetry ping is generated for each click action performed on the same button.
[Notes]:
- This issue is reproducible on both "Treatment A" and “Treatment B" branches of the experiment.
- This issue is also reproducible by multiple clicking the “Next” button without previously selecting any radio button.
- This is NOT reproducible when clicking the “Skip this step” button multiple times.
- Here is a screen recording of the issue.
I don't think this will be a blocker for the experiment and I believe this will require an on-train fix to resolve. But pinging product to verify!
Flags: needinfo?(nbulous)
Correct, it would be nice to have fixed but is not a blocker, especially since it requires on-train work.
Flags: needinfo?(nbulous)
Updated•2 years ago
|
Assignee: nobody → jprickett
Priority: -- → P2
Updated•2 years ago
|
Iteration: --- → 122.1 - Nov 20 - Dec 1
Updated•2 years ago
|
Points: --- → 2
Updated•2 years ago
|
Iteration: 122.1 - Nov 20 - Dec 1 → 122.2 - Dec 4 - Dec 15
Updated•2 years ago
|
Iteration: 123.1 - Dec 18 - Dec 29 → 123.2 - Jan 1 - Jan 12
Updated•2 years ago
|
Iteration: 123.2 - Jan 1 - Jan 12 → 123.3 - Jan 15 - Jan 19
Updated•2 years ago
|
Iteration: 123.3 - Jan 15 - Jan 19 → 124.1 - Jan 22 - Feb 2
Updated•2 years ago
|
Blocks: ms-deployments
Updated•2 years ago
|
Iteration: 124.1 - Jan 22 - Feb 2 → 124.2 - Feb 4 - Feb 16
Updated•2 years ago
|
Iteration: 124.2 - Feb 4 - Feb 16 → 125.1 - Feb 19 - Mar 1
Updated•2 years ago
|
Iteration: 125.1 - Feb 19 - Mar 1 → ---
Updated•1 year ago
|
Assignee: jprickett → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•