Closed Bug 436250 Opened 16 years ago Closed 15 years ago

Livemarks can't be disabled at runtime

Categories

(Firefox :: Bookmarks & History, defect)

3.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mikeperry.unused, Unassigned)

Details

The livemarks service has no pref that can disable fetching of livemarks for a period of time. The pref browser.bookmarks.livemark_refresh_seconds in toolkit/components/places/src/nsLivemarkService.js is only checked in the constructor, and the closest you can get to disabling the service is to set it to a really large number of seconds, which only has effect once the browser is restarted.

This could be fixed with a separate pref, or perhaps by making _shutdown() a scriptable idl-published call and moving the addObserver for the bookmarks service from the LivemarkService constructor to startup(). I think the latter is probably the cleaner approach. Any problems with this approach?
Component: Bookmarks → Places
OS: Windows XP → All
QA Contact: bookmarks → places
Hardware: PC → All
Note: this issue also applies to livebookmarks under FF2, but a fix doesn't look like it would be nearly as clean.
we have stopUpdateLivemarks and start API methods in livemarkService
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
See also bug 499568
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
You need to log in before you can comment on or make changes to this bug.