If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Livemarks don't automatically update.

VERIFIED INVALID

Status

()

Firefox
Bookmarks & History
VERIFIED INVALID
10 years ago
4 years ago

People

(Reporter: tracy, Unassigned)

Tracking

Trunk
Points:
---
Bug Flags:
blocking-firefox3 +

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
Gavin requested I file this instead of reopening bug 419832.  It probably should have been bug 419885 that got reopened (which was supposedly fixed by bug 390505.  Anyway, livemarks are not refreshing automatically.

Feeds aren't automatically updating with latest nightly builds. However, I just grabbed a build on Windows (20080308) for the day after the fix went in to bug 419832. (20080307) It doesn't work as you might expect there either.
Flags: in-litmus?
Flags: blocking-firefox3?
Blocking, but I find this hard to believe, since my "Latest Headlines" feed has an article about the cyclone in Burma, which definitely happened more recently than the creation of this profile.
Flags: blocking-firefox3? → blocking-firefox3+
(Reporter)

Comment 2

10 years ago
according to bug 419832 per marco: you should check that livemark check happens after about 5s from ui startup and then every 5 minutes...

refresh is definitely not happening in those time frames. 

(In reply to comment #2)
> according to bug 419832 per marco: you should check that livemark check happens
> after about 5s from ui startup and then every 5 minutes...
> 
> refresh is definitely not happening in those time frames. 
> 

That's not correct. See the code here:

http://mxr.mozilla.org/seamonkey/source/toolkit/components/places/src/nsLivemarkService.js#190

5 seconds after startup, the livemark service's update timer is started. The update timer fires immediately, and then every 15 minutes thereafter (by default, but you can tweak it here: browser.bookmarks.livemark_refresh_seconds).

When the update timer fires, it iterates over the list of livemarks, and will refresh a livemark *only* if it's expired, which is determined here:

http://mxr.mozilla.org/seamonkey/source/toolkit/components/places/src/nsLivemarkService.js#190

The TTL of a livemark is determined here, using nsICacheEntryInfo.expirationTime (ie: as specified by the server), or 1 hour if the server did not specify:

http://mxr.mozilla.org/seamonkey/source/toolkit/components/places/src/nsLivemarkService.js#190
Regardless of what we figure out here, I'll update the code w/ comments to ease understanding of this, as well as update the MDC docs.
(Reporter)

Comment 5

10 years ago
Invalid:  I let my Windows box sit with FX open for a couple hours without doign anything on it.  I don't the time frame, but the del.icio.us/recent feed *did* update automatically.

Thanks for the clarification dietrich.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID

Comment 6

10 years ago
sorry the initial refresh happened every 5 minutes, final patch uses expire time / 4 so 15 minutes (max 1h). i pointed bad timings on that comment
(Reporter)

Comment 7

10 years ago
no problem, Marco. I can go verify the others now. :-)
Status: RESOLVED → VERIFIED
Updated the wiki: http://developer.mozilla.org/en/docs/Using_the_Places_livemark_service#Update_Behavior
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
(Reporter)

Comment 10

4 years ago
removing in-litmus flag, it no longer exists
Flags: in-litmus?
You need to log in before you can comment on or make changes to this bug.