If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[meta] Sidebar Search panel tracking bug

NEW
Unassigned

Status

SeaMonkey
Sidebar
15 years ago
7 years ago

People

(Reporter: Erich 'Ricky' Iseli, Unassigned)

Tracking

(Depends on: 4 bugs, {meta})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
This bug lists all problems related to the Search panel in the sidebar.
(Reporter)

Comment 1

15 years ago
65863,162416,149631,57855,161534,45082,161592,161537,53840,30997,116584,157239,
117612,147068,153050,152430,150337,151026,145301,62061,37875,127540,57859,64984,
52316,95885,89385,76204,104413,76080,71532,38454,99834,148921
Keywords: meta
(Reporter)

Updated

15 years ago
(Reporter)

Comment 2

15 years ago
I'm sorry for the spam folks. I got the dependencies the wrong way round.
(Reporter)

Updated

15 years ago
Depends on: 170540
(Reporter)

Comment 3

15 years ago
=> Sidebar
Component: Search → Sidebar
(Reporter)

Updated

15 years ago
Depends on: 177614
(Reporter)

Updated

15 years ago
Depends on: 185126
(Reporter)

Updated

15 years ago
Depends on: 182523

Updated

14 years ago
Depends on: 190341

Updated

14 years ago
Depends on: 243093
Product: Browser → Seamonkey

Updated

13 years ago
Depends on: 296235
Assignee: samir_bugzilla → nobody
QA Contact: claudius → sidebar

Comment 4

8 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 5

8 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

Comment 6

8 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

Comment 7

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

Comment 8

7 years ago
Expiring meta bugs is pure nonsense.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: EXPIRED → ---

Updated

7 years ago
Status: REOPENED → NEW
You need to log in before you can comment on or make changes to this bug.