Closed Bug 1787128 Opened 3 years ago Closed 3 years ago

Stop composing error state fluent message identifiers in Firefox View

Categories

(Firefox :: Firefox View, task, P2)

Unspecified
All
task
Points:
1

Tracking

()

RESOLVED FIXED
106 Branch
Tracking Status
firefox106 --- fixed

People

(Reporter: Gijs, Assigned: mconley)

References

(Blocks 1 open bug)

Details

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

Attachments

(1 file)

See discussion on https://phabricator.services.mozilla.com/D154675 .

Rather than having a specialcase for 1 string at https://searchfox.org/mozilla-central/rev/30ac44262374be08ccd4262ee36f0716152868d3/browser/components/firefoxview/tab-pickup-container.mjs#167-170 , let's use a mapping from error state to string identifiers. This has the benefits that it's easy to update just 1 string identifier in future, and that it's easy to figure out where strings are used by just searching for string identifiers.

Severity: -- → S3
Priority: -- → P1
Priority: P1 → P2
Assignee: nobody → mconley
Status: NEW → ASSIGNED

While this introduces some redundancy, the advantage to spelling out the error message IDs like
this explicitly is that if the string ever needs to be updated (which requires a message ID
change), then we have a single place to remap the error code strings to the message IDs.

Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c50a8b342d63 Explicitly define TabPickupContainer's error message IDs rather than composing them. r=sclements
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: