10 Commits (3678b124e0a037871b1b7f0b36c18feb166fdd6a)

Author	SHA1	Message	Date
Alexandru2909	3678b124e0	For #24790 - Remove Event.wrapper for home screen related telemetry	2 years ago
mcarare	cb14837bc6	For #24098: Update tests for tabs tray metrics.	2 years ago
Roger Yang	047ec890b2	Closes #22550: Refactor search term tab grouping logic to rely on middleware	2 years ago
Gabriel Luong	dc15ee2415	For #22488 - Fix intermittent test failure with InactiveTabsControllerTest	3 years ago
Jonathan Almeida	08b15689b1	Close #22305: Use TabsTrayStore for populating adapters	3 years ago
Jonathan Almeida	9bb49585ea	No issue: Merge our inactive tab interactor/controllers	3 years ago
Jonathan Almeida	9cef9357b1	Close #20704: Add AppStore to Components	3 years ago
Jonathan Almeida	7666f0e4c2	No issue: Replace TabsTray.Tab with TabSessionState ... Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>	3 years ago
Mugurell	09e8d34c26	For #20507 - Inactive tabs telemetry ... Two new events are added: - "inactive_tabs_expanded" for when the inactive tabs section is expanded - "inactive_tabs_collapsed" for when the inactive tabs section is collapsed For tracking when an inactive tab is opened / closed I've repurposed the existing tabs tray telemetry (since the functionality uses the same code) - tabs_tray.opened_existing_tab - tabs_tray.closed_existing_tab to support an extra "source" key indicating the feature from which a tab was opened or closed. The current values for this new key are: - "Tabs tray" for when a tab was opened/closed from tabs tray - "Inactive tabs" for when a tab was openes/closed from the Inactive tabs section of the tabs tray.	3 years ago
Jonathan Almeida	d6bc93981d	Issue #20663: Make inactive card collapsible ... We use make the inactive tabs section of the tabstray collapsible in this change, with a technical quirk: we want to make the "isExpanded" state of the tabs stay for the lifetime of the app and not the tabs tray, but this functionality does not exist. In this patch, we're storing the UI state in a singleton class that exists for the lifetime of the app, but a more concrete solution is to use an AppStore that holds content like this, which we can land in a future patch.	3 years ago