Closed Bug 1788257 Opened 2 years ago Closed 2 years ago

Firefox View: Colorways expiration string is unclear if referring to colorway or collection

Categories

(Firefox :: Firefox View, defect, P1)

Firefox 106
Desktop
All
defect
Points:
1

Tracking

()

VERIFIED FIXED
106 Branch
Tracking Status
firefox106 --- verified

People

(Reporter: pbothun, Assigned: dao)

References

(Blocks 1 open bug)

Details

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

Attachments

(4 files)

Actual: When a user navigates to Firefox View and has already selected a colorway, the colorway collection graphic and name is replaced with the active colorway and the expiration notice remains.

Recommendation: Revise the "Expires January 23" string mention the collection name or allude to the collection expiring to alleviate concern that the active colorway will expire on this date.

Flags: needinfo?(pbothun)
Component: General → Firefox View
Whiteboard: [fidefe-2022-mr1-firefox-view]
Severity: -- → S4
Priority: -- → P3

Let's revisit this UX post MR. Thanks Phil!

Flags: needinfo?(pbothun)

The order also isn't right in this view:

1. Name of colorway
2. Date of expiration of collection
3. Variation of colorway
4. Button to change colorway

Colorway name (1) and variation (3) should be proximal to each other.

I am leaning towards we remove the Expiration pill entirely in this selected state. The user can always see expiration of the collection itself within the picker modal.

Thanks for the comment here Meridel! I think we should probably split these asks into 2 separate bugs for easier tracking? re: 1) Content/Copy order and 2) Removal of expiry pill in selected state.

I just got a chance to speak with Dao on this as well and wanted to propose an alternative solution. Would it be acceptable to flip the position of the pill and the variation name + collection name? This way, the expiration would be visually tied to the collection instead of the colorway itself. What do you think?

Flags: needinfo?(mwalkington)

If I understand Dao's suggestion correctly, I don't think flipping the order in this view would fix the issue. It would still appear as if the Colorway itself is expiring when it is actually the collection.

Flags: needinfo?(mwalkington)

Dao -- Let's just remove the pill in the selected state. That will resolve the concerns around the ordering. Do we need design direction on spacing?

Flags: needinfo?(jberman)
Flags: needinfo?(dao+bmo)

Right now it's

<Colorway applied>
<Collection><Colorway balance>
<expiration>
CTA

We might want to consider

<Colorway applied><Colorway balance>
<Collection><expiration>
CTA

Or, removing the pill in the selected state we would have

<Colorway applied><Colorway balance>
<Collection>
CTA

Attaching a screenshot of what option 2 here could look like for reference

Flags: needinfo?(jberman)

Here's a link to a modified design file where we just remove the pill

https://www.figma.com/file/0eNvH6AAW9qKLypuFTIeuP/Fx-View-Colorways-applied?node-id=426%3A13087

Thanks Josh! I think we probably go with the option to remove the pill only as bringing the intensity up in line with the colorway name would cause complexity for l10n, right?

Flags: needinfo?(francesco.lodolo)

(In reply to Ray Fambro from comment #8)

Thanks Josh! I think we probably go with the option to remove the pill only as bringing the intensity up in line with the colorway name would cause complexity for l10n, right?

We have until Wednesday/Thursday, in principle (string freeze starts Friday the 16th, but we'd need to move pretty quickly and be confident the new thing is definitely what we want.

Flags: needinfo?(francesco.lodolo)

I don't feel confident in <Colorway applied><Colorway balance> in the title, especially given the timing (this Friday the whole company is off).

From a localization perspective, I would just remove the expiration bit, and leave further experiments for 107.

(In reply to Francesco Lodolo [:flod] from comment #10)

From a localization perspective, I would just remove the expiration bit, and leave further experiments for 107.

Agreed. Localization itself aside, pulling the intensity up would increase the chance of the title wrapping, which all in all seems like a step backwards.

Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Points: --- → 1
Flags: needinfo?(dao+bmo)
Blocks: firefox-view

Agreed Flod and Dao. Thanks for getting us to a solution here. Appreciate you working this into the queue!

Severity: S4 → S2
Priority: P3 → P1
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6bb6eba9a1a2
Hide collection expiry date when a colorway is selected. r=bigiri
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch

I can confirm that the expiry date is no longer displayed in Firefox view after a colorway is selected on Windows 10x64, macOS 11, and Ubuntu 21.04 with Firefox 106.0b2 (20220920185943).

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

Attachment

General

Creator:
Created:
Updated:
Size: