Closed Bug 1304524 Opened 8 years ago Closed 7 years ago

Consider filtering out default bookmarks (about:firefox, android.mozilla.org, support.mozilla.org) in Activity Stream highlights

Categories

(Firefox for Android Graveyard :: Activity Stream, defect, P3)

Product:
Firefox for Android Graveyard
Component:
Activity Stream
Type:
defect

Tracking

(firefox52 wontfix)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox52 --- wontfix

People

(Reporter: ahunt, Unassigned)

References

Details

(Whiteboard: [MobileAS])

1. Start with a fresh fennec build (with AS enabled) 2. Enable Activity Stream pref 3. View about:home - about:home is shown as the (only) highlight Extra: 4. Dismiss that highlight (using the WIP context menu) 5. addons.mozilla.org appears in it's place. 6. Dismiss that highlight 7. support.mozilla.org appears (8. Dismiss that highlight -> no more highlights are shown) Do we want to show these default bookmarks in Activity Stream? This probably isn't an issue for early testing of AS (most users should have higher ranked history and newer bookmarks), but it could be an issue for new installs if/when AS is made the default. Somewhat related: do we need an empty state screen?
Whiteboard: [MobileAS]
I've just realised that we specifically restrict ourselves to showing at most 1 bookmark in getHighlights, so items 4-8 are actually expected behaviour. (long bookmarkLimit = 1)
I guess we need to think about "onboarding" or the empty state in general - If I remember correctly desktop already had a simple solution for this (hardcoded highlights to start with).
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
Rank: 1
Priority: -- → P3
All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.
Component: Awesomescreen → Activity Stream
I've never seen this happen before (in fact, we had to add a highlights empty state!) so I don't think it's relevant anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.