138508 - bookmark scheduler should allow multiple day choices

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Ketan Gangatirkar]

The bookmark scheduler for checking a site for updates should allow the user to
specify arbitrary sets of days.  In the current implementation, if I have a site
that gets updated MWF at arbitrary times, my best option is to check on all
weekdays.

Comment 1

[mental]

I think this is pretty much bug 109195.  Recommend duping this bug, and moving
that one to Bookmarks.

Comment 2

[Jason Bassford]

Hmm.  See bug 109195 comment 3.  That bug is about *always* opening a page at
set times.  This one is about checking for updates at set times.  In this bug,
if there are no updates the page should not be displayed.

Possibly, bug 109195 could be modifed to include initiating a page update check
as "an event", in addition to simply displaying a page, but I think it would be
cleaner to keep the bugs separate for now.

I would have an interest in this bug on its own - and I don't believe it should
be platform specific: confirming and changing to All.

The "When" selection box should allow you to Ctrl-Click on multiple entries. 
(Or the UI could be altered altogether to turn it into a series of check boxes.)
 If you do something stupid like picking "Every day" AND "Mondays" that would be
your fault and the latter should be ignored rather than run twice on Mondays.

Comment 3

[Ben Goodger (use ben at mozilla dot org for email)]

Mass reassign of my non-Firefox bugs to [e-mail]

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420