Following the designs in Figma[1], implement an onboarding callout template for profiles. The action called when the callout button is clicked will be defined in bug 1918536. See additional details/requirements in [2]. [1] https://www.figma.com/design/FXL6eQGaZ3MI50XebsCIJ8/Profiles?node-id=9450-133488&t=K4uQvSjrVaOGDrBJ-4 [2] https://docs.google.com/document/d/1PW6AuB1PR4BAbskODGDGsd5rrmDcyu72m7iT1yc5xJ0/edit#heading=h.kup321pjdow2
Bug 1918543 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Following the designs in Figma[1], implement an onboarding callout template for profiles. The action called when the callout button is clicked will be defined in bug 1918536. See additional details/requirements in [2]. As part of this bug, we'll need to understand and document how the feature callout ID maps to some telemetry probe value. [1] https://www.figma.com/design/FXL6eQGaZ3MI50XebsCIJ8/Profiles?node-id=9450-133488&t=K4uQvSjrVaOGDrBJ-4 [2] https://docs.google.com/document/d/1PW6AuB1PR4BAbskODGDGsd5rrmDcyu72m7iT1yc5xJ0/edit#heading=h.kup321pjdow2
Following the designs in Figma[1], implement an onboarding callout template for profiles. The action called when the callout button is clicked will be defined in bug 1918536. See additional details/requirements in [2]. As part of this bug, we'll need to understand and document how the feature callout ID maps to some telemetry probe value. Because this feature goes in the Nimbus dashboard, not in the Firefox source code, it can happen after 134 goes to Beta (although we don't want to block Nimbus QA from testing the callout, so not too much later). [1] https://www.figma.com/design/FXL6eQGaZ3MI50XebsCIJ8/Profiles?node-id=9450-133488&t=K4uQvSjrVaOGDrBJ-4 [2] https://docs.google.com/document/d/1PW6AuB1PR4BAbskODGDGsd5rrmDcyu72m7iT1yc5xJ0/edit#heading=h.kup321pjdow2