Closed
Bug 523524
Opened 15 years ago
Closed 7 years ago
Places UI: Bookmarks, tags, and history ranges should be viewable in the content area
Categories
(Firefox :: Bookmarks & History, enhancement)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: faaborg, Assigned: faaborg)
References
(Blocks 1 open bug, )
Details
(Keywords: meta)
Note: this is a meta tracking bug for UI mockups and discussion of the overall user experience.
Any collection of pages in places grouped by a folder, tag, or a specific history range needs to be able to be able to be rendered in a content area page. For 3.7 we will like start with just displaying the page title, url, and favicon for each item, and then expand on this in 4 to include thumbnail images.
Also for 3.7 we may decide to make this page static and non-interactive, so that for instance the user can't modify the contained bookmarks or history items (moving, renaming, deleting, etc.) During this phase the Library window will still be be required for these types of organization tasks, and the content area pages will simply serve as an easier way for the user to browse to bookmarks and history.
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
note: for 3.7, this will not have thumbnails, will be text only. alex is going to make a mockup for this.
Comment 3•15 years ago
|
||
notes:
- can bookmark/save a non-folder view? (history range, search results) - not for 3.7.
- no paging (async containers)
- throbber for loading large pages
- larger icon for header
Comment 4•15 years ago
|
||
This seems to go hand in glove with the query api, so i'll take it.
Assignee: faaborg → ddahl
Assignee | ||
Comment 6•15 years ago
|
||
we can unmeta it, really whatever works best for the places team. I kind of like to keep these open until the release though (while implementation level bugs close and then follow ups are filed).
Comment 7•15 years ago
|
||
I think there will be several bugs in implementing this functionality. Perhaps we can enumerate those tasks here and file implementation bugs that block this one.
also: We might want to study how Thunderbird accomplished this in its search interface.
Tasks I can think of:
1. Model-View-Controller implementation for content pages
a. Model seems to correspond to an implementation-specific wrapper for the new Query API.
b. View seems to be a templating tool (and implementation DOM helpers) for content (which I assume will be XHTML)
c. Controller seems to be an object that will help deal with content/chrome security and execution of functions that display the view and deal with observers and events.
Besides the work in Thinderbird 3, what else might be a good reference for this?
Comment 8•15 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".
In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body contains places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.
Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.
Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Updated•13 years ago
|
Summary: Places UI (3.7): Bookmarks, tags, and history ranges should be viewable in the content area → Places UI: Bookmarks, tags, and history ranges should be viewable in the content area
Updated•10 years ago
|
Severity: normal → enhancement
Status: NEW → ASSIGNED
Target Milestone: Firefox 4.0 → ---
Version: Trunk → unspecified
Comment 9•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•