Closed
Bug 497606
Opened 16 years ago
Closed 12 years ago
In the tags service, use the result api for all tasks rather than using both the result api and observers
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: asaf, Unassigned)
References
Details
(Keywords: perf)
In the tags service, use the result api for all tasks rather than using both the result api and observers.
| Reporter | ||
Updated•16 years ago
|
Comment 1•16 years ago
|
||
ideally we want to strip out tags from bookmarks, so this would be a step back, imo. result should not be used at all if we do the above.
Comment 2•16 years ago
|
||
also actually we use bookmarks observer to eventually remove tags when a bookmark is removed.
Comment 3•16 years ago
|
||
ugh, we had several bugs from using the result api inside of the backend services like tags and livemarks, usually involving things like bookmark restore iirc.
Comment 4•16 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
Comment 5•12 years ago
|
||
using results in tagging service caused more perf issues than benefits, and we want to remove them from bookmarks, so this is a wontfix imo.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•