Closed Bug 1699892 Opened 4 years ago Closed 4 years ago

Hook up the server-side generated default FxA icons

Categories

(Firefox :: Toolbars and Customization, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
89 Branch
Tracking Status
firefox-esr78 --- fixed
firefox88 --- fixed
firefox89 --- fixed

People

(Reporter: sfoster, Assigned: dcoates)

References

(Blocks 1 open bug)

Details

(Whiteboard: [proton-icons])

Attachments

(2 files)

Once the work to implement the new alpha-numeric default avatar icons is complete on the server-side, we need to hook them up in the various FxA toolbar buttons and surfaces

Jira ticket for the server-side work: https://jira.mozilla.com/browse/FXA-3181

Severity: -- → S3
Priority: -- → P2

Part of the work here will be to allow the domain that we serve the icons up from to use -moz-context-properties. I spoke to dholbert about this, and apparently this can be done by adding that domain to the allow-list in here somehow: https://searchfox.org/mozilla-central/rev/4e87b5392eafe1f1d49017e76f7317b06ec0b1d8/layout/svg/SVGContextPaint.cpp#28-74

This allow/disallow list is less about security, and more about making sure we don't accidentally ship this in a way that sites start using, since it's non-standard.

The server-side FxA work is happening here: https://github.com/mozilla/fxa/pull/7972

The production domain for these images will be profile.accounts.firefox.com.

Priority: P2 → P3

Romain - this is almost ready to land on the server side and it will begin setting default avatars immediately. Do you need us to delay landing the change to coordinate with a date or Firefox launch?

Flags: needinfo?(rtestard)

(In reply to Wil Clouser [:clouserw] from comment #4)

Romain - this is almost ready to land on the server side and it will begin setting default avatars immediately. Do you need us to delay landing the change to coordinate with a date or Firefox launch?

Is this change impacting release or only nightly initially?
Did UX review the icons that are produced? (color, font, size....)?

Flags: needinfo?(rtestard) → needinfo?(wclouser)

It would be great if you could share sample icons so UX can review. Amy confirmed she had reviewed the sample available in Figma (circle with M).
Assuming UX is happy with the implementation it sounds like we should turn that on for nightly, I was assuming that this change would not make it, this is great!

Yes, Danny worked with Amy on the icons. @danny - could you attach some samples here?

FxA is a website and doesn't differentiate Nightly or Release, so, when this lands it would go out to all users of FxA regardless of browser or device. Do you want us to delay landing or follow FxA's normal release schedule? (Right now that would have this live around April 21)

Flags: needinfo?(wclouser)
Flags: needinfo?(rtestard)
Flags: needinfo?(dcoates)
Attached image monograms.png (deleted) —

Here's a monogram avatar with context-fill enabled/disabled for a few themes.

Flags: needinfo?(dcoates)

(In reply to Wil Clouser [:clouserw] from comment #7)

Yes, Danny worked with Amy on the icons. @danny - could you attach some samples here?

FxA is a website and doesn't differentiate Nightly or Release, so, when this lands it would go out to all users of FxA regardless of browser or device. Do you want us to delay landing or follow FxA's normal release schedule? (Right now that would have this live around April 21)

Thanks will, it sounds like we could deploy to all channels but is there a way we could test this first?

Flags: needinfo?(rtestard)

Once we land it, it will be on our staging server. Do you have someone in QA you'd like us to ping once it is on staging?

ni'ing tracy on comment 10

Flags: needinfo?(twalker)

(In reply to Wil Clouser [:clouserw] from comment #10)

Once we land it, it will be on our staging server. Do you have someone in QA you'd like us to ping once it is on staging?

Yes, Alin is already cc'd here.

Flags: needinfo?(twalker)

For testing, Firefox needs to be configured with the stage FxA servers. Us devs usually use fxa-dev-launcher to do it automatically. https://github.com/mozilla/fxa/blob/main/packages/fxa-dev-launcher/README.md

This is on our staging server, scheduled to go out around April 21. Alin - could you look at this?

Assignee: nobody → dcoates
Flags: needinfo?(alin.ilea)

Out of curiosity, what is the domain for the staging server?

Flags: needinfo?(wclouser)

Ah, I thought Danny's link up there would have it, but it's pretty barebones. Stage is at https://accounts.stage.mozaws.net/ . Rebecca Billings would have more testing docs if they are needed (and we're in #fxa).

Flags: needinfo?(wclouser)

Sure, I'll take a look. Thanks!

Flags: needinfo?(alin.ilea)
Depends on: 1703588
Blocks: 1703588
No longer depends on: 1703588
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bbce2c52a886 Allow the Firefox Accounts avatar server to use SVG context properties. r=dholbert
Regressions: 1703735
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch

Comment on attachment 9214217 [details]
Bug 1699892 - Allow the Firefox Accounts avatar server to use SVG context properties. r?dholbert!

Beta/Release Uplift Approval Request

  • User impact if declined: Firefox Accounts users using the built-in light theme with no custom avatar set will have a harder time seeing the new monogrammed avatar when the panel is open. The new monogrammed avatar hasn't shipped yet, but will likely ship soon.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This is well contained, well understood code, with an automated test.
  • String changes made/needed: None.
Attachment #9214217 - Flags: approval-mozilla-beta?

Comment on attachment 9214217 [details]
Bug 1699892 - Allow the Firefox Accounts avatar server to use SVG context properties. r?dholbert!

Unfortunate that we can't segment by train, but glad we got it sorted now in the cycle. Approved for 88.0b9. Is this needed on ESR78 also?

Flags: needinfo?(dcoates)
Attachment #9214217 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Flags: needinfo?(mconley)

Hm... I guess, that makes sense, yes.

Flags: needinfo?(mconley)

Comment on attachment 9214217 [details]
Bug 1699892 - Allow the Firefox Accounts avatar server to use SVG context properties. r?dholbert!

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: This isn't a security bug, but we might want to consider it for aesthetics, since it will mean that in Light Mode, the default FxA avatar will be hard to see.
  • User impact if declined: See beta uplift request.
  • Fix Landed on Version: 89
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): See beta uplift request.
  • String or UUID changes made by this patch: None.
Attachment #9214217 - Flags: approval-mozilla-esr78?

Comment on attachment 9214217 [details]
Bug 1699892 - Allow the Firefox Accounts avatar server to use SVG context properties. r?dholbert!

Approved for 78.10esr.

Attachment #9214217 - Flags: approval-mozilla-esr78? → approval-mozilla-esr78+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: