1555299 - [Firefox Accounts page] Continue button from Join Firefox section flickers

Status: RESOLVED WORKSFORME

(www.mozilla.org :: Pages & Content, defect)

Description

[Raluca Popovici, Desktop QA]

Attachment: Firefox Account.html

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

1. Launch Firefox with an user not logged into a Firefox Account
2. Open the attached html on browser
3. Click on Firefox Accounts link
4. Verify that the CTA to Join Firefox is properly displayed on new Firefox accounts page

Actual result:
Continue button from Join Firefox section flickers. See video attached.

Expected result:
Continue button from Firefox is properly displayed and doesn't flicker.

Comment 1

[Raluca Popovici, Desktop QA]

Attachment: 2019-05-29_11h52_32.mp4

Comment 2

[Eric Renaud [:erenaud]]

Amy - please take a look at this issue QA reported when testing the Trailhead WNP.

Comment 3

[Craig Cook (:craigcook)]

You're viewing the page on https://bedrock-demo-craigcook.oregon-b.moz.works but I believe the test plan only included instructions for whitelisting https://www-demo2.allizom.org in browser.uitour.testingOrigins. If you whitelist the new server name in the same way, that flicker shouldn't happen. And this won't be an issue in production because www.mozilla.org is already whitelisted.

So this is expected behavior when uitour is unavailable.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Tania, can you ask your team to retest to make sure that this works as described in comment 3?

Craig, I'm a little worried that we may miss something if we just close this type of bug without actually re-testing.

Comment 5

[Luciana queirolo]

(In reply to Craig Cook (:craigcook) from comment #3)

You're viewing the page on https://bedrock-demo-craigcook.oregon-b.moz.works but I believe the test plan only included instructions for whitelisting https://www-demo2.allizom.org in browser.uitour.testingOrigins. If you whitelist the new server name in the same way, that flicker shouldn't happen. And this won't be an issue in production because www.mozilla.org is already whitelisted.

So this is expected behavior when uitour is unavailable.

HI,
Should we retest this in the current build or do we need a new one?

thanks,

Comment 6

[Luciana queirolo]

Hi,

As previously discussed with Craig I edited the pref "rowser.uitour.testingOrigins" in about:config and added the value "https://bedrock-demo-craigcook.oregon-b.moz.works" and the flicker stopped.

Hope this helps!

Comment 7

[Liz Henry (:lizzard) (relman/hg->git project)]

Great, sounds like it was just a testing setup issue then.