1865847 - [Experiment] The Pin notification can be displayed twice in the `control` branch

Status: NEW

(Firefox :: Messaging System, defect, P2)

Description

[Ciprian Muresan [:cmuresan], Ecosystem QA]

[Affected versions]:

• Firefox Release 120.0 - Build ID: 20231116134553
• Firefox Beta 121.0b1 - Build ID: 20231120154937

[Affected Platforms]:

• Windows 11 Build 22631 (23H2)
• Windows 11 Build 22621 (22H2)

[Prerequisites]:

• Have the nimbus.debug pref set to true on a new clean profile.
• Have the messaging-system.rsexperimentloader.collection_id pref set to nimbus-preview on the same profile used above.
• Firefox is not default the default browser and it is not pinned to the taskbar.

[Steps to reproduce]:

1. Open the browser with the profile from prerequisites.
2. Copy and paste the following link in a new tab: about:studies?optin_slug=windows-11-pinning-api-experiment&optin_branch=control&optin_collection=nimbus-preview.
3. Navigate to the about:welcome page.
4. Click the Save and continue button.
5. Dismiss the notification.
6. Focus the browser and click the back arrow.
7. Click the Save and continue button and observe the behavior.

[Expected result]:

• Nothing happens.

[Actual result]:

• The Pin notification is displayed a 2nd time.

[Notes]:

• The issue is also reproducible when enrollment in the experiment is done naturally.
• The notification is only displayed twice. Repeating the steps will not make the notification re-appear as many times as the Save and continue button is clicked.
• The issue is not reproducible on the treatment-a branch.
• I could not reproduce the issue on the Nightly channel, because the notification is not triggered at all there. I'm assuming this has something to do with the channel and not the build.
• Attached is a screen recording of the issue: link

Comment 1

[Emily McMinn :emcminn]

Since the control branch is the current experience, any bugs that are showing up in it are also currently happening in release. Since we want to know what effect the current (kinda broken) experience is having, I'd say this isn't a blocker for the experiment.

That being said, I'll leave the bug open so that we can fix the issue separately from the experiment, assuming we keep the current experience.

Comment 2

[Punam Dahiya [:pdahiya]]

Including product to help triage and prioritize this issue

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:lsmith, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.