Closed
Bug 1318549
Opened 8 years ago
Closed 7 years ago
[AS] [Highlights] Ensure that highlights algorithm is the same as desktop one
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1312016
People
(Reporter: Grisha, Unassigned)
References
Details
(Whiteboard: [MobileAS])
When AS user is using Sync to sync data across devices, it seems pertinent that they have a consistent experience with Highlights. That is, when switching from device to device, their highlights should remain the same. Ensuring that highlight algorithms are the same will help here. Possible complication are sync intervals. If user picks up a mobile device which hasn't synced yet, or their desktop didn't sync yet, their highlights will possibly differ. Based on the highlights algorithm this might or might not be a problem. Additionally, as part of this bug I'd like to investigate whether an opposite of this makes sense - that we have highlights tailored to the platform. Both on Android and iOS we track local vs remote visits, so it's possible to prioritize locally visited websites when generating highlights.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P2
Summary: [Highlights] [AS] Ensure that highlights algorithm is the same as desktop one → [AS] [Highlights] Ensure that highlights algorithm is the same as desktop one
Reporter | ||
Comment 1•8 years ago
|
||
Note to self: similarly to how we're going to prioritize local history for Top Sites in Bug 1321368, can we do something similarly simple for Highlights as well?
Updated•7 years ago
|
Iteration: --- → 1.13
Priority: P2 → P1
Updated•7 years ago
|
Iteration: 1.13 → 1.14
Comment 2•7 years ago
|
||
I'm going to close this as duplicate of bug 1312016: The new implementation is following the desktop implementation very closely.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•