bookmark scheduler will ignore bookmarks if not enough check time given



15 years ago
14 years ago


(Reporter: long, Assigned: p_ch)


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (X11; U; IRIX64 IP35; en-US; rv:1.7.3) Gecko/20041012
Build Identifier: Mozilla/5.0 (X11; U; IRIX64 IP35; en-US; rv:1.7.3) Gecko/20041012

I have somewhere around 340 bookmarks that I had scheduled to check for updates
from 9 AM to 6 PM every 60 minutes.  The bookmark scheduler loops through the
bookmarks and picks a new one to check every 15 seconds it appears.  Thus, in
about 1 hour it can check 240 bookmarks.  However, when it gets to the end of
the hour it goes back to the beginning of the bookmarks and starts checking them
again because 60 minutes has passed.  Thus the 100 bookmarks at the end of my
file never get checked for updates, all without any kind of warning.  If I set
all the bookmarks to be checked every 240 minutes then everything works as
expected.  I would expect Mozilla to either warn the user or to automatically
adjust things so that all bookmarks get checked.

Reproducible: Always
Steps to Reproduce:
1. Create set of 340 bookmarks.
2. Schedule them to check for updates all day long every 60 minutes.

Actual Results:  
Only the first 240 or so ever get checked for updates.

Expected Results:  
Either warn me that update checking won't function properly or automatically
adjust to check all the bookmarks.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.