Closed Bug 254297 Opened 18 years ago Closed 10 years ago

Batch bookmark properties - scheduling, notification

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: bfults, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [2012 Fall Equinox])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2

A useful feature regarding the bookmarks would be if a user could batch edit
properties of bookmarks. There would be two main methods for batching: setting
properties on a bookmarks folder, which would then be inhertied by the children,
or selecting multiple bookmarks (using shift/ctrl) in the Bookmark Manager and
selecting Properties from the right-click context menu.

This way a user could set a single schedule or notification method for an entire
folder (or arbitrary selection) of bookmarks. This is a feature already present
in most UIs dealing with multiple objects and their properties (e.g. Windows
Explorer).

Reproducible: Always
Steps to Reproduce:
1. Open Bookmarks Manager

2. Right-click on a bookmark folder and select Properties
3.  Observe that there is only an "Info" tab for the folder itself.

-or-

2. Select multiple bookmarks and right-click on one of them.
3. Notice that the Properties option is disabled on the context menu.


Expected Results:  
There could be settings regarding the properties of the bookmarks in a specific
folder and properties of selected groups of bookmarks.
Product: Browser → Seamonkey
Reassigning as per Bug #32644
Assignee: p_ch → nobody
Depends on: 330392
First part is covered by Bug 330392, second, about notifications, became obsolete with removing that feature, so is this bug still need to be open?
Whiteboard: [2012 Fall Equinox]
Nope. Rule is one bug per issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.