(meta) Task Continuity 2.0

RESOLVED INVALID

Status

()

RESOLVED INVALID
4 years ago
6 months ago

People

(Reporter: designakt, Unassigned)

Tracking

({meta})

38 Branch
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ux])

How can the user access links saved/remembered by the browser for them.

This will reconsider the Library as a way to access Links, provide alternative ideas and define the relation of different kinds of saved/remembered Links.

Currently the following kinds of saved/remembered links exist and might be extend in future with new features as considered in an extended share Mechanism (https://bugzilla.mozilla.org/show_bug.cgi?id=1135028)

History, Tabs, Tab Groups, Frequently Visited Pages, Unsorted Bookmarks, Filed Bookmarks, Tagged Bookmarks, Toolbar Bookmarks, Recent Bookmarks, Mobile Bookmarks, Reading List … 

Possible options are a reconsidered New Tab Page, more prominence for Sidebars, extended Bookmark Toolbar etc…

Updated

4 years ago
Flags: qe-verify-
Flags: firefox-backlog+
Whiteboard: [ux]

Updated

4 years ago
Assignee: nobody → mjaritz
Status: NEW → ASSIGNED
Iteration: --- → 39.1 - 9 Mar
Points: --- → 13

Updated

4 years ago
Iteration: 39.1 - 9 Mar → 39.2 - 23 Mar

Updated

4 years ago
Iteration: 39.2 - 23 Mar → 39.3 - 30 Mar

Updated

4 years ago
Iteration: 39.3 - 30 Mar → 40.1 - 13 Apr
Summary: [UX] Reconsider saved/remembered Links retrieval (Bookmarks, History, Reading List … ) → (meta) Task Continuity 2.0

Updated

4 years ago
Assignee: mjaritz → nobody
Status: ASSIGNED → NEW
Iteration: 40.1 - 13 Apr → ---
Points: 13 → ---
Flags: qe-verify-
Flags: firefox-backlog+
Keywords: meta
No longer blocks: 1125237
Mistakenly filed against Firefox 38 and should be instead 38 Branch. Sorry for the spam. dkl
Version: Firefox 38 → 38 Branch
Closing as it is not relevant anylonger and parts have been implemented in different ways.
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.