1817144 - Study interferes with RTAMO onboarding being displayed

Status: NEW

(Firefox :: Messaging System, defect, P3)

Description

[Alex Cornestean]

Description:
The RTAMO onboarding page is not displayed when launching the browser due to possible interference from an active study - Window Modal vs Tab Modal.

Upon browser launch following the initiation of the RTAMO flow, a modal is displayed showing the default Firefox onboarding and not the RTAMO onboarding.

After completing the default Firefox onboarding, accessing about:welcome will show the RTAMO page and the RTAMO flow can be completed i.e. the add-on can be installed.

Steps to reproduce:

1. Using a VM with Windows, launch Edge or Chrome
2. Navigate to AMO and access the page of an add-on
3. Click the “Download Firefox and get the extension” button on the add-on’s page
4. Once the installer is downloaded, run it to install Firefox
5. After installation, Firefox will launch in a Window Modal due to the study being active and display the default onboarding and not the RTAMO onboarding as would be expected

Actual:
The RTAMO onboarding page is not displayed when Firefox launches.

Expected:
The RTAMO onboarding page should be displayed when Firefox launches.

Comment 1

[William Durand [:willdurand]]

:pdahiya Hi! After Bug 1698153, I thought this was not supposed to happen anymore. WDYT?

Comment 2

[Punam Dahiya [:pdahiya]]

Hi William

Thanks for filing, this is expected for users enrolled in Treatment branches of window vs tab modal study, which is using modal to display onboarding and bypass content checks and redirection done when onboarding is opened using about:welcome URL. I will appreciate if you can add telemetry seen for IMPRESSION and CLICK event ping in Browser Console with steps in #comment 0 (steps to re-trigger modal onboarding and see telemetry are below) , this will help account how many users in release are seeing this experience.

1. Set below prefs in about:config
   browser.ping-centre.log=true
   browser.newtabpage.activity-stream.telemetry=true
   messaging-system.log=debug
   browser.aboutwelcome.log=debug

2. In browser console run below script
   Cc["@mozilla.org/browser/clh;1"].getService().wrappedJSObject.firstRunProfile = true; Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._maybeShowDefaultBrowserPrompt()

UJET Dashboard https://mozilla.cloud.looker.com/dashboards/109 shows about 750 users in EN locale that visits RTAMO onboarding page. Study is enrolling windows users in EN locale for a week. Including data science so that they can account for RTAMO users in their analysis. Thanks

Comment 3

[William Durand [:willdurand]]

RTAMO isn't currently implemented in the "window modal" and the check previously introduced in Bug 1698153 is skipped, which is why RTAMO isn't excluded here and also why we don't see any RTAMO screen.

Comment 4

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

Set release status flags based on info from the regressing bug 1801224

:nsauermann, since you are the author of the regressor, bug 1801224, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

Comment 5

[Negin]

We will be waiting on the results of the experiment/study to determine whether we move forward with this feature. We will be addressing this bug if we decide to implement the feature in production.