Closed Bug 1816522 Opened 1 year ago Closed 1 year ago

[Tabs tray to Compose] Add multi selection banner UI

Categories

(Fenix :: Tabs, task, P3)

All
Android

Tracking

(firefox114 fixed)

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: 007, Assigned: aputanu)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid])

Attachments

(2 files)

When the Tabs Tray is multi select mode, the page indicator UI should be replaced by the multi selection banner. The close, "X", button should be plumbed with its logic (i.e. returning to the page indicator banner) with this story. The number of tabs selected should also be functioning after this ticket.

In the present XML version, the UI lives across TabsTrayFragment, components_tabstray2.xml, and SelectionBannerBinding.

Have placeholder click lambdas for the icon buttons.

Add

  • "X selected" UI with correct number of selected tabs
  • Icons for bookmark & share & three-dot

Bookmark, share, and three dot menu functionality will be handled in

Blocks: 1816555
Blocks: 1816556
Blocks: 1816558
Depends on: 1816743
Severity: -- → N/A
Summary: [Tabs tray to Compose] Add multi selection banner → [Tabs tray to Compose] Add multi selection banner UI

Note from Jonathan: We should consider making the MultiSelectBanner to support different options in case we'd like to add the selection functionality to Private or Synced tabs at a future time.

Assignee: nobody → aputanu
Status: NEW → ASSIGNED

(In reply to Alexandru Putanu [:aputanu] from comment #2)

Note from Jonathan: We should consider making the MultiSelectBanner to support different options in case we'd like to add the selection functionality to Private or Synced tabs at a future time.

I think this makes sense. I would just caution against over-engineering anything from the beginning, as this will be fairly simple to refactor in the future, compared to the XML counterpart.

We also don't know yet what this could hypothetically look like, so any work we do today to try to accommodate potential use cases could also need to be refactored anyway to support the actual ask from product/UX down the road.

Blocks: 1826994
Depends on: 1828684
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: