Closed Bug 224154 Opened 22 years ago Closed 22 years ago

Context Menu Extension broken in 10/24/2003 Firebird nightly

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: mmoy, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031015 Firebird/0.7 (aebrahim) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031024 Firebird/0.7 (aebrahim) Context Menu Extensions (see http://white.sakura.ne.jp/~piro/xul/_ctxextensions.html.en) stopped working with the 10/24/2003 nightly build. It worked fine with the 10/23/2003 nightly build from aebrahim. The extension installs but the feature is non-functional. Trying to use it results in some joavscript errors if you have the JavaScript Console is up and running. I had a look at the checkins from 10/23 to 10/24 and didn't see anything obvious that would affect this area. The author of the extension, Piro, is apparently busy as posts to his private forum at http://white.sakura.ne.jp/~piro/xul/forum/ about this and a few other problems haven't been answered for a few days. Reproducible: Always Steps to Reproduce: 1. Intall the extension. 2. Restart the browser. 3. Select Preferences from the Extensions menu, change something, exit preferences, and then go into preferences again. The setting shouldn't be set. It may be that the preferences dialog doesn't even show up. Alternately, right click for the context menu and all the options show up. Actual Results: One of the problems in the JavaScript console is "ExtService Has No Properties" Expected Results: The expected results for the right-click context menu is a fairly short context menu. You can normally add entries via the preferences.
a) wrong Product (because this seem to be a firebird extension) b) this is invalid because it's unclear if the extension is broken or if there is a bug in Mozilla. The author of an extension can create a bug if he finds a bug in Mozilla
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
The extensions was released on October 3, 2003 and I tested it with almost every version of Firebird up to and including October 24, 2003. What I'm looking for is the checkin from the 23rd to the 24th that resulted in the problem or some kind of pointer as to how to fix the problem myself. The author of the extension does not visit Mozillazine and, I suspect, does not visit Bugzilla. He has asked me to file bugs on his behalf in the past.
Verified not a SeaMonkey bug. Please file firebird bugs on Firebird.... I assume that you know about bonsai and can look up checkins?
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.