1795832 - The “Continue to Firefox accounts” tab is not focused after clicking the “Sign in” link from the intro screen of the “about:welcome” page

Status: RESOLVED WONTFIX

(Firefox :: Messaging System, defect, P4)

Description

[Simona Rosu [:srosu], Ecosystem QA]

Attachment: ContinueToFxa_NotFocused.gif

[Affected versions]:

• Firefox Nightly 108.01 (Build ID: 20221017213658)
• Firefox Beta 107.0b1 (Build ID: 20221017134228)

[Affected Platforms]:

• Windows 10 x64
• macOS 12.5.1
• Linux Mint 20.2 x64

[Prerequisites]:

• Have the Firefox browser installed and opened.
• Have the “browser.aboutwelcome.templateMR” pref set to true.

[Steps to reproduce]:

1. Navigate to the “about:welcome” page.
2. Click the “Sign in” link from the top-right corner of the page.
3. Observe what happens.

[Expected result]:

• The “Continue to Firefox accounts” page is opened in a new tab, and it is focused.

[Actual result]:

• The “Continue to Firefox accounts” page is opened in a new tab and is not focused.

[Notes]:

• Attached is a screen recording of the issue.

Comment 1

[Ania]

This is expected behavior, as we don't want users to exit the onboarding flow and likely not return (as sign-in is a fairly long process). And the recover is very easy - if users want to continue with sign in without completing the onboarding, they can switch the tab. We also have less than ~4% percent of users signing, so unless we receive a strong signal that users are unhappy with this, I'm inclined to keep this behavior as is.

Comment 2

[Emily McMinn :emcminn]

(In reply to Ania from comment #1)

This is expected behavior, as we don't want users to exit the onboarding flow and likely not return (as sign-in is a fairly long process). And the recover is very easy - if users want to continue with sign in without completing the onboarding, they can switch the tab. We also have less than ~4% percent of users signing, so unless we receive a strong signal that users are unhappy with this, I'm inclined to keep this behavior as is.

I was about to comment as well that this behaviour is governed by a pref (browser.tabs.loadInBackground) so while I think it's possible to force focus, users might perceive it as ignoring their preference. (Right now loadInBackground defaults to true; the signin link does get focus if the user has switched the pref to false.)

Should we keep this open for a while and keep an eye on it, or it is ok to resolve as WONTFIX?

Comment 3

[Ania]

Ah, that makes sense. I'd be comfortable resolving it as won't fix, and I'll keep an eye on feedback about it in the MR feedback tracker doc.

Comment 4

[Emily McMinn :emcminn]

Sounds good!