Closed Bug 2030715 Opened 3 months ago Closed 3 days ago

Nova redesign for Extensions panel

Categories

(Toolkit :: Add-ons Manager, task, P3)

task
Points:
1

Tracking

()

RESOLVED FIXED
154 Branch
Tracking Status
firefox154 --- fixed

People

(Reporter: sthompson, Assigned: mhynson)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [fidefe-nova])

Attachments

(5 files)

UX spec: https://www.figma.com/design/XT0eDYh4RtbMNWaYQi0efM/Chrome-Sidebar-UX-Specifications--Sprint-1-?node-id=14540-28811&t=DmWtRyDhwG2zsfvj-0

Expected changes based on Figma:

Given the nature of these changes, it will be easier to switch these out in the codebase without making them conditional on the Nova pref.

I noticed the FIDEFE link. Does that mean that you're going to work on this task?

P.S. Linking bug 2032049 for visibility - the Nova redesign caused a bug in the visibility of extension icon button's icon still unresolved. We should make sure that Nova restyling does not cause such regressions.

Flags: needinfo?(sthompson)
See Also: → 2032049

During the Nova redesign planning process, a number of panels including the Extensions panel were lumped into the "Chrome/Sidebar" category that the Firefox Desktop Front-End team is planning to tackle.

Since the UX spec looks like all of the visual changes should come from general design system + chrome CSS changes that Firefox Desktop Front-End will be making in general, I think it's reasonable for our team to make sure that the Extensions panel looks correct after our changes.

So far, the only real changes that have occurred behind browser.nova.enabled are design system CSS property changes that are cascading throughout the browser. We are only now starting to go through each part of the browser to make any fixes, adjustments, or other redesigns.

If your team is planning on making any content or visual design changes to the Extensions panel in the next several months, then we can chat to plan that work.

Flags: needinfo?(sthompson)

Thanks Stephen, based on your reply we are triaging this as P3 N/A, but if you determine that anything should be done specifically for the extension panel let us know so that we can bump the priority and support that effort if necessary.

Severity: -- → N/A
Priority: -- → P3

Hi folks,
Noting that one thing that needs to be updated for the Extensions panel is the empty state illustration for the extensions panel.

The assets for Classic window have been finalized and is available here - https://www.figma.com/design/XT0eDYh4RtbMNWaYQi0efM/Chrome-Sidebar-UX-Specifications--Sprint-1-?node-id=29192-25685&t=4HuqwiySeSiphGy4-0

Extensions panel empty state is also different in the Private Window (I attached a screenshot of how it looks like now). We were hoping to figure out if it's easy for us to use two different illustrations, one in Classic, one in Private, or whether this would be fairly tricky and should be treated as a nice to have and addressed post-Nova?

Flags: needinfo?(git)
Flags: needinfo?(sthompson)
Flags: needinfo?(lgreco)
Flags: needinfo?(git)

Based on https://searchfox.org/firefox-main/rev/43aae7a9ab016c3892591a759e48ff73896287e4/browser/base/content/browser-addons.js#2442-2507 I think it would be relatively simple to have two illustrations in the DOM and show/hide the appropriate illustration based on whether the current window is a private window or not. I would just make sure we're clear about the expectation: I'm assuming that we want the private window variant to always show in the empty state of all private windows, regardless of whether a user has no extensions, extensions without private window permissions, or disabled extensions.

Flags: needinfo?(sthompson)

Thank you, Stephen, this is very helpful context.
Kate and Michelle will decide tomorrow whether to use a separate illustration for the Private window.

If we decide to do it, let's indeed use the same illustration for each of these special states:

I would just make sure we're clear about the expectation: I'm assuming that we want the private window variant to always show in the empty state of all private windows, regardless of whether a user has no extensions, extensions without private window permissions, or disabled extensions.

I updated my earlier comment with a link to the finalized illustration for the Classic window empty state.

Assignee: nobody → mhynson

Confirming that Kate and Michelle decided to have the same illustrations in classic and private window for Nova.

They will connect with Karen and Jane to do a bigger audit to see if a separate private window illustration style makes sense, but it's out of scope for Nova.

I exported the new illustration from Figma and ran it through https://svgomg.net/ to optimize it. This attachment should be ready to replace https://searchfox.org/firefox-main/source/browser/themes/shared/addons/extensions-panel-empty-illustration.svg in the codebase.

Attachment #9606008 - Attachment description: Bug 2030715 - Update the Extensions panel empty state. r=#fluent-reviewers,sclements,scolville,kpatenio → Bug 2030715 - Update the Extensions panel empty state. r=#fluent-reviewers
Attachment #9607247 - Attachment description: WIP: Bug 2030715 - Updates menu item button icon for the items in Extension panel. → Bug 2030715 - Updates menu item button icon for the items in Extension panel.

Clearing old needinfo (patches are already attached to phabricator and are already being reviewed).

Flags: needinfo?(lgreco)
Pushed by mhynson@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/5742aa5c71fa https://hg.mozilla.org/integration/autoland/rev/5512e51458b4 Update the Extensions panel empty state. r=fluent-reviewers,desktop-theme-reviewers,bolsson,robwu,dao
Status: NEW → RESOLVED
Closed: 3 days ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: