Skip to content

task(settings): add fallback text for linked account 3rd-party auth#19450

Merged
toufali merged 1 commit intomainfrom
add-fallback-separator-text
Sep 18, 2025
Merged

task(settings): add fallback text for linked account 3rd-party auth#19450
toufali merged 1 commit intomainfrom
add-fallback-separator-text

Conversation

@toufali
Copy link
Copy Markdown
Member

@toufali toufali commented Sep 15, 2025

Because

  • we want to ensure fallback text in the event fluent lookup fails

This pull request

  • refactors to allow fallback text

Issue that this pull request solves

Closes: FXA-12397

Other information (Optional)

In response to #19441 (comment)

@toufali toufali requested a review from a team as a code owner September 15, 2025 22:50
deeplink?: string;
flowQueryParams?: QueryParams;
separatorTextId?: string;
separatorText?: string;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to be pushing back so much heh😅

We've kind of conventionally called this something like, localizedSeparatorText to indicate the text being passed in does not need localization (search the codebase for localizedHeading, localizedDescription, localizedText, localizedCTAText, and there are others). I think we should either have every instance of this component have that localized text passed into it (using ftlMsgResolver and not l10n because that enforces fallback text is provided and we hope to turn l10n tests on for one of these days which also would have caught the missing ID!), or we can pass in a prop like separatorType instead which can default to "or". Then, you can conditionally render the correct <FtlMsg> based on separatorType. Dealer's choice!

Also... our #9E9E9E text-grey-300 does not pass AA ADA color contrast even at "normal" text, so at "extra light", it most certainly should be darkened.

image image

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LZoog see latest! Does that work? I didn't test text-grey-600 because my local is still broken 😮‍💨 Happy to change if needed!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per discussion AA standard request completed via #19485

@toufali toufali force-pushed the add-fallback-separator-text branch 2 times, most recently from 2a16c36 to 3e0813a Compare September 16, 2025 23:54
Copy link
Copy Markdown
Contributor

@LZoog LZoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you for sticking with this!!

Mentioned this in Slack but bonus points also if we get a new storybook state added for ThirdPartyAuth, that's a non-blocking request though 🙂

@toufali toufali force-pushed the add-fallback-separator-text branch from 3e0813a to d5930f0 Compare September 18, 2025 16:03
@toufali toufali merged commit 057bf2b into main Sep 18, 2025
19 checks passed
@toufali toufali deleted the add-fallback-separator-text branch September 18, 2025 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants