Closed
Bug 2047660
Opened 2 months ago
Closed 1 month ago
Spike: Evaluate approaches for Auto Tab Grouping
Categories
(Core :: Machine Learning: Frontend, task)
Core
Machine Learning: Frontend
Tracking
()
RESOLVED
FIXED
People
(Reporter: Mardak, Unassigned)
References
()
Details
(Whiteboard: [aiaug])
Local-first clustering and tab group naming leveraging the models we have in CW.
Proactively suggest grouping when the following happens:
Browser session starts
Switch to Smart Window
Suggest max 3 groups so that it’s not overwhelming. It’s better to leave some tabs ungrouped than force grouping everything and scare the users away. If there are remaining ungrouped tabs that could have been grouped, offer users to “group more”.
User should be able to review, move across, or remove any tab within a suggested grouping.
Once grouped, user can undo the entire process. (user can already ungroup any existing group)
Updated•2 months ago
|
Spike documentation. Can fill in more detail as necessary, if I missed anything: here
| Reporter | ||
Updated•1 month ago
|
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•