Closed Bug 1542866 Opened 5 years ago Closed 4 years ago

[meta] Add server-controllable collapsible sections to Discovery Stream - TBD

Categories

(Firefox :: New Tab Page, enhancement, P2)

Product:
Firefox
Component:
New Tab Page
Type:
enhancement
Points:
5

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: k88hudson, Assigned: thecount)

References

Details

(Keywords: meta)

Attachments

(1 file)

Link to GitHub pull-request: https://github.com/mozilla/activity-stream/pull/5195
52 bytes, text/x-github-pull-request
Details | Review
No description provided.
Summary: Add collapsible sections to Discovery Stream → [meta] Add collapsible sections to Discovery Stream
Summary: [meta] Add collapsible sections to Discovery Stream → [meta] Add server-controllable collapsible sections to Discovery Stream
Depends on: 1543442
Depends on: 1535773

I don't think the remainder of this work is in scope for 68. There needs to be breakdown of the API for the server to specify the header of a section and what rows/components fall into that section. On the client side, there also needs to be work to keep state of whether a section is collapsed or not as well as potentially allowing sections to be removed (??). There's also product/design questions of what should be allowed or not, e.g., collapsible section that is in a single column?

Blocks: pocket-newtab
No longer blocks: pocket-newtab-68
Type: defect → enhancement
Summary: [meta] Add server-controllable collapsible sections to Discovery Stream → [meta] Add server-controllable collapsible sections to Discovery Stream - TBD
Priority: -- → P2
Component: Activity Streams: Newtab → New Tab Page
Assignee: nobody → sdowne

how far can we get without changing the schema?

Iteration: --- → 70.2 - Jul 22 - Aug 4
Points: --- → 5
Priority: P2 → P1

Done for this = collapsible + dismissable.
Handling dismissable in collection work in 70

Assignee: sdowne → nobody
Iteration: 70.2 - Jul 22 - Aug 4 → ---
Priority: P1 → P2
Assignee: nobody → sdowne

We've solved for this in a few different ways since. Closing this bug. We'll make a new one if we need something else/like this in the future. \o/

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.