nsButtonPrefListener in editor.js deals with pref variable which is not defined

RESOLVED EXPIRED

Status

SeaMonkey
Composer
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Mikhail Khlopotov, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
A nsButtonPrefListener function in editor/editor.js :
  try {
   var pbi = pref.QueryInterface(Components.interfaces.nsIPrefBranchInternal);
   pbi.addObserver(this.domain, this, false);
pref is not defined anywhere, so this function does nothing.

pref should probably be changed to gPrefs or this function removed at all since
I don't see any use of it

Comment 1

16 years ago
-->brade
Assignee: syd → brade
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All

Comment 2

15 years ago
Daniel--long ago you checked in this code.  Do you know what it's intended use
is?  It doesn't seem like it works at all (see previous comments).  Can it be
removed?
Assignee: brade → glazman
Product: Browser → Seamonkey
Assignee: daniel → nobody
QA Contact: sujay → composer

Comment 3

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 4

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.