Closed Bug 1795752 Opened 2 years ago Closed 2 years ago

Sign in/sign up to FxA should use entrypoint=fx-view

Categories

(Firefox :: Firefox View, defect)

defect

Tracking

()

VERIFIED FIXED
108 Branch
Tracking Status
firefox106 + verified
firefox107 --- verified
firefox108 --- verified

People

(Reporter: sfoster, Assigned: sfoster, NeedInfo)

References

Details

(Whiteboard: [fidefe-2022-mr1-firefox-view] )

Attachments

(2 files)

We currently build a URL to open the sign-in/signup to FxA tab using "firefoxview" as the entry point. That should be "fx-view".

i.e. https://accounts.firefox.com/?context=fx_desktop_v3&entrypoint=firefoxview&action=email&service=sync
vs.
https://accounts.firefox.com/?context=fx_desktop_v3&fx-view=firefoxview&action=email&service=sync

This bug doesn't appear to impact end-user functionality, but it complicates/confuses reporting etc. on the backend.

Assignee: nobody → sfoster
Status: NEW → ASSIGNED
Pushed by sfoster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d734d1d10478 Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r=Gijs

Backed out for causing mochitest failures on browser_feature_callout.js

Flags: needinfo?(sfoster)

Thanks for the backout - it didn't occur to me to go looking for a test that relied on this detail.

Flags: needinfo?(sfoster)
Pushed by sfoster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/83cd5e5f031c Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r=Gijs
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch

Comment on attachment 9298898 [details]
Bug 1795752 - Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r?Gijs!

Beta/Release Uplift Approval Request

  • User impact if declined: None, impact is to reporting.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: Verify that clicking the "Continue" button to sign in to Fxa on firefox view loads https://accounts.firefox.com/ with an entrypoint=firefoxview querystring param
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): No functional changes, single line change that only affects firefox view.
  • String changes made/needed: None
  • Is Android affected?: No
Attachment #9298898 - Flags: approval-mozilla-beta?
Flags: qe-verify+

Leif, i'm told this should be on your radar as it may have an impact on FxA reporting. My understanding is that firefox view was opening the FxA page with an incorrect entrypoint querystring param, which would mean they might show up as originating from the appmenu.

Flags: needinfo?(loines)

We were definitely seeing some data coming from entrypoint=firefoxview before, as seen in this chart.

But thanks for flagging me, I can update the dashboards to look for either entrypoint value now.

Flags: needinfo?(loines)

Comment on attachment 9298898 [details]
Bug 1795752 - Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r?Gijs!

Approved for 107.0b2.

Attachment #9298898 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-triaged]

Comment on attachment 9298898 [details]
Bug 1795752 - Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r?Gijs!

Beta/Release Uplift Approval Request

  • User impact if declined: None, impact is to reporting.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: Verify that clicking the "Continue" button to sign in to Fxa on firefox view loads https://accounts.firefox.com/ with an entrypoint=firefoxview querystring param
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): No user-visible functional changes, single line change that only affects firefox view and how FxA sign up page loads are attributed.
  • String changes made/needed: None
  • Is Android affected?: No
Attachment #9298898 - Flags: approval-mozilla-release?

Comment on attachment 9298898 [details]
Bug 1795752 - Use fx-view rather than firefoxview as the entry point param for FxA signin/signup. r?Gijs!

Looks like this patch doesnt apply cleanly on 106. I'll prepare a new patch.

Attachment #9298898 - Flags: approval-mozilla-release?

This the same as attachment 9298898 [details], but some refactoring in there since 106 meant it didn't apply cleanly. This does the same thing.

Try push: https://treeherder.mozilla.org/jobs?repo=try&revision=e63fa18e1a45a32b5419923e1648a212954a8faf

Beta/Release Uplift Approval Request

  • User impact if declined: None, impact is to reporting.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: Verify that clicking the "Continue" button to sign in to Fxa on firefox view loads https://accounts.firefox.com/ with an entrypoint=firefoxview querystring param
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): No user-visible functional changes, single line change that only affects firefox view and how FxA sign up page loads are attributed.
  • String changes made/needed: None
  • Is Android affected?: No
Attachment #9299182 - Flags: approval-mozilla-release?

Verified that the issue is fixed in Firefox 107.0b2 and Firefox 108.0a1 across platforms (Windows 10x64, Ubuntu 18.4 and macOS 10.12.6).
Marking the issue Fx106-affected based on the previous comments.

[Tracking Requested - why for this release]:

Would like to ensure that we are capturing accurate data with our telemetry. The sooner we can make this update, the better.
@Sam - Can you give a perspective on the level of risk associated with uplifting?

Flags: needinfo?(sfoster)

(In reply to Ray Fambro from comment #16)

[Tracking Requested - why for this release]:

Would like to ensure that we are capturing accurate data with our telemetry. The sooner we can make this update, the better.
@Sam - Can you give a perspective on the level of risk associated with uplifting?

This is on the low end of low risk from the desktop perspective. Its a small patch, no tricky logic or gotchas and easy to unambiguously verify. We should get the FxA folks to confirm this fixes their reporting gap however.

Flags: needinfo?(sfoster)

Thanks Sam! Pulling in Vesta to continue the thread.

Flags: needinfo?(vzare)

Comment on attachment 9299182 [details] [diff] [review]
bug-1795752-v106.diff

Approved for 106.0.2

Attachment #9299182 - Flags: approval-mozilla-release? → approval-mozilla-release+

Verified as fixed with Firefox 106.0.2 Windows 10x64, macOS 10.12.6 and Ubuntu 20.4.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: