Missing "Open web page in a new Tab" in bookmark schedule (notify)/bookmark update notifier

RESOLVED EXPIRED

Status

SeaMonkey
Tabbed Browser
P3
enhancement
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Sascha Claus, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
1) Edit the properties for a bookmark
2) Activate Tab "Schedule"
3) Make a timetable
4) Activate Tab "Notify"
5) 4 options, among other things: "Open web page in new window"

But there is no "Open web page in new tab" pref.
tabbed browser.
Assignee: pchen → hyatt
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: Bookmarks → Tabbed Browser
Ever confirmed: true
QA Contact: claudius → sairuh

Comment 2

17 years ago
Reassigning to new component owner.
Assignee: hyatt → jaggernaut

Comment 3

17 years ago
-> ben, p3, future
Assignee: jaggernaut → ben
Priority: -- → P3
Target Milestone: --- → Future
QA Contact: sairuh → claudius

Comment 4

16 years ago
*** Bug 138512 has been marked as a duplicate of this bug. ***
(Reporter)

Comment 5

16 years ago
more keywords into the summary
Summary: "Open web page in a new Tab" in bookmark schedule (notify) missing → Missing "Open web page in a new Tab" in bookmark schedule (notify)/bookmark update notifier

Comment 6

15 years ago
*** Bug 174212 has been marked as a duplicate of this bug. ***
Assignee: bugs → nobody
QA Contact: claudius → tabbed-browser
(Assignee)

Updated

10 years ago
Product: Core → SeaMonkey

Comment 7

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

Comment 8

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.