'schedule' and 'notify' bookmarks globally

RESOLVED EXPIRED

Status

SeaMonkey
Bookmarks & History
P5
enhancement
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Claudius Gayle, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
***Overview Description: 
  This is basically and RFE but I also believe it's a 4xp bug. Bear with me for a minute as you read.
NS6's Bookmark scheduling features are far more robust than 4.x's ever were but one important
aspect is missing; in 4.x you could easily see if any or all of your bookmarks had changed without
any effort. There was a 2-or-3 stage icon change that probably no one understood. We now have
that same ability in seamonkey and the controls are even more fine-tuned but we are missing the
ability to easily watch ALL of the bookmarks. All of the scheduling and notifications are on a case-
by-case ie individual bookmarks basis. This leads to a tedious process if ther are many you want
to watch, so tedious it's likely a deterrent.
4.x automatically watched them all for you.   

I have a solution. Why don't we just implement the schedule and notify tabs for Folders?
In this way a user could select their root bookmark folder and apply the feature, or select any
arbitrary folder. The possibilities this would open up are endless and amazing! The only nit to work
out is conflicting prefs. I'd suggest that schedule prefs for individual bookmarks always override
folders by default (you'd state this in the schedule tab of the folder) and you could also include
a checkbox that says override schedule and notification options for bookmarks contained within.

Comment 1

17 years ago
Looks like an excellent idea. It would make bookmarks more configurable, and 
save time in setting up individual subscriptions, while keeping stuff out of 
the prefs dialog.

The only tricky bit I can think of would be working out what to do with 
bookmarks (or subfolders, even) when you moved them from one folder to another 
folder which had different subscription settings.
(Reporter)

Comment 2

17 years ago
*** Bug 75323 has been marked as a duplicate of this bug. ***

Comment 3

17 years ago
great idea!

severity normal -> enhancement?
priority -> p3?
mozilla 1.0 keyword?
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.

Assignee: ben → pchen
Status: ASSIGNED → NEW

Comment 5

17 years ago
Mass move Ben's bugs dumped on me marked future with p5 to get off my untriaged
radar. You can filter out this email by looking for "ironstomachaussie"
Priority: -- → P5

Comment 6

17 years ago
mass reassign of pchen bookmark bugs to ben
Assignee: pchen → ben

Comment 7

17 years ago
*** Bug 121751 has been marked as a duplicate of this bug. ***

Comment 8

16 years ago
Severity: enhancement
Severity: normal → enhancement

Comment 9

16 years ago
*** Bug 131585 has been marked as a duplicate of this bug. ***

Comment 10

16 years ago
This enhancement is dependent on bug 51207.
Depends on: 51207
(Reporter)

Comment 11

16 years ago
carrying over the nsbeta1 nomination from bug 121751
Keywords: nsbeta1
(Reporter)

Updated

16 years ago
Keywords: 4xp
(Reporter)

Comment 12

16 years ago
*** Bug 121751 has been marked as a duplicate of this bug. ***

Comment 13

16 years ago
Nav triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-

Comment 14

16 years ago
*** Bug 156991 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
No activity here in a couple of years.  Firefox needs bookmarks checking support
and this feature would be a good addition overall to the Mozilla software.

Comment 16

14 years ago
There is an extension for Firefox called Bookmarks Linkchecker that performs a
check of all bookmarks and flags those that are new. While not perfect, it's a
good enough extension to make do with.

http://www.google.com/url?sa=U&start=1&q=http://extensionroom.mozdev.org/more-info/bookmarkchecker&e=9901
Assignee: bugs → nobody
QA Contact: claudius → bookmarks

Comment 17

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 18

9 years ago
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 19

9 years ago
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 20

9 years ago
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 21

9 years ago
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 22

9 years ago
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 23

8 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.