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)

Desktop
Windows
defect
Points:
2

Tracking

()

Tracking Status
firefox119 --- affected
firefox120 --- affected

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.debug pref set to true;
    browser.ping-centre.log pref set to true;
  • Have the "Browser Console" opened.

[Steps to reproduce]:

  1. Open the browser with the profile from the prerequisites.
  2. 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.
  3. Restart the browser.
  4. Navigate to “about:welcome”.
  5. Click any of the radio buttons from the Survey screen.
  6. Click the “Next” button multiple times.
  7. 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)
Assignee: nobody → jprickett
Priority: -- → P2
See Also: → 1716007
Iteration: --- → 122.1 - Nov 20 - Dec 1
Points: --- → 2
Iteration: 122.1 - Nov 20 - Dec 1 → 122.2 - Dec 4 - Dec 15
Iteration: 122.2 - Dec 4 - Dec 15 → 123.1 - Dec 18 - Dec 29
Iteration: 123.1 - Dec 18 - Dec 29 → 123.2 - Jan 1 - Jan 12
Iteration: 123.2 - Jan 1 - Jan 12 → 123.3 - Jan 15 - Jan 19
Iteration: 123.3 - Jan 15 - Jan 19 → 124.1 - Jan 22 - Feb 2
Iteration: 124.1 - Jan 22 - Feb 2 → 124.2 - Feb 4 - Feb 16
Iteration: 124.2 - Feb 4 - Feb 16 → 125.1 - Feb 19 - Mar 1
Iteration: 125.1 - Feb 19 - Mar 1 → ---
Assignee: jprickett → nobody
See Also: → 1995698
You need to log in before you can comment on or make changes to this bug.