[Tab Groups] Tab groups aren't always displayed when first created
Categories
(Firefox for Android :: Tabs, defect)
Tracking
()
People
(Reporter: 007, Assigned: 007)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group4])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
About 1/10 times, when creating your first tab group, the group will get created but NOT displayed. Instead, the tab manager will display a stale state of no tab groups in the tab grid/list. When this occurs, the tab group page will either show the tab group with zero tabs, or it will not display any tab groups at all.
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
Pairing with Julie, we found that there was a race condition with how the data was being emitted from the database, where the tab group metadata and the tab group's list of tab IDs were emitting separately and would overlap each other when creating the UI data model.
We found that having one Flow emitting all of the data instead of two Flows emitting the data separately solves this issue.
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Comment 4•2 months ago
|
||
| bugherder | ||
Comment 5•2 months ago
•
|
||
Reproduced the issue with a Vivo V23 (Android 14) device on RC 152 Firefox for Android.
Comment 6•2 months ago
•
|
||
The patch landed in nightly and 152 is affected.
:007, is this bug important enough to require an uplift?
- If yes, please nominate the patch for Release approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox152towontfix.
For more information, please visit BugBot documentation.
Comment 7•2 months ago
|
||
Verified on the latest Firefox for Android Nightly 153.0a1 from 6/11 using a Vivo v23 (Android 14), and a Pixel 6 (Android 17).
Comment 8•2 months ago
|
||
firefox-release Uplift Approval Request
- User impact if declined/Reason for urgency: A subset of users will have a degraded experience, perceiving the app/feature is broken during the first interaction with creating a tab group.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: Create a tab group via drag and drop (or multiselection)
Delete the tab group and try again, if the group is created
- Risk associated with taking this patch: medium
- Explanation of risk level: The risk touches how tab group data is read-in from the database. The scope of changes is small, but it involves a core code area.
This change has been baking in Nightly and 153 beta, and it's been verified in Nightly.
- String changes made/needed?: N/A
- Is Android affected?: yes
| Assignee | ||
Comment 9•2 months ago
|
||
This required changing the Tab Group repo to emit one Flow instead of one per data model (one for group meta data and one for tab group assignments). This was a bit of a jenga block change, and it required some structural changes to our tests and repo code.
This also introduces two new data models:
- TabGroupData
- This is the new data class wrapper for everything being emitted from the repo.
- TabGroup
- This is a new data class so the underlying database model does not have to leak through the codebase.
Some repo operations were also removed if they were only being used inside of tests.
This patch also fixes a typo with the tab group assignment data model.
Original Differential Revision: https://phabricator.services.mozilla.com/D305413
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 10•2 months ago
|
||
| uplift | ||
Comment 11•2 months ago
|
||
Added to the 152.0.2 relnotes.
Comment 12•2 months ago
|
||
Verified on the latest Firefox for Android 152.0.2 version, using a Samsung Galaxy S24 (Android 16), and a Pixel 6 (Android 17).
Description
•