Closed Bug 523520 Opened 15 years ago Closed 11 years ago

[meta][project] Places UI

Categories

(Firefox :: Bookmarks & History, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Firefox 4.0

People

(Reporter: faaborg, Assigned: faaborg)

References

(Depends on 1 open bug, )

Details

(Keywords: meta)

      No description provided.
Note: this is a meta tracking bug to organize a collection of UI mockups (in dependent bugs) and for discussion of the overall user experience of Places in Firefox 4.
Depends on: 524056
Depends on: 524057
Depends on: 524059
Depends on: 524062
No longer depends on: 524062
Depends on: 524069
Depends on: 524074
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
Is there a bug around to discuss general ideas proposed in UI mockups (like https://wiki.mozilla.org/Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh)?
(In reply to comment #3)
> Is there a bug around to discuss general ideas proposed in UI mockups (like
> https://wiki.mozilla.org/Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh)?
Bugs are not the place for dicussions.  That's what the newsgroups are for.
Summary: [meta] Places UI Changes in Firefox 4.0 → [meta][project] Places UI
Depends on: PlacesInTabLibrary
while the single bugs may still matter, this meta bug is pointless now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.