Closed Bug 283454 Opened 19 years ago Closed 19 years ago

Regression (since 20050222) Certain extensions break/can cause freezes after new build

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ronin2040, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20050206 Firefox/1.0 (Firefox CE 1.0 P4W-X22)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20050223 Firefox/1.0 (MOOX2)

Since the change in how extensions are registered (I guess) in the 02/23
version, certain extensions (particularly Sage 1.3.1) cease to work and can
cause freezes--icons for sage disappear from all places and the menu item
disappears.

Further, on clicking the "options" button from extensions manager, Firefox
completely freezes.  I doubt this is a specific extension problem since sage has
worked fine on many other versions, both official and unofficial builds
(Community edition--20050206, Moox 20050219, official 20050222, moox 20050222).

Reproducible: Always

Steps to Reproduce:
1.Install the new 20050223 build
2.Install sage (if not already installed)
3.Open extension manager
4.Attempt to open "options" for sage

Actual Results:  
Sage icons are gone from toolbar customization menu, and clicking options
freezes firefox.

Expected Results:  
Icons should have remained, options button should have worked

I've checked this using many themes, on both official and unofficial builds,
with both existing and fresh sage installs.

I also think that the extension "preferential", which has worked fine in all
builds I've tried since the 1.0 release, kind of "breaks" in some of the latest
builds--opening the "advanced preferences" menu item populates the dialog box
with  nothing.
related to Bug 278534 I guess
Version: unspecified → Trunk
Same thing for MAS trunk builds. Workaround for the extensions: reinstall all
extensions. See bug 278534 comment 25 and
http://wiki.mozilla.org/index.php/Gecko:Chrome_Registration#Compatibility. AFAIK
an existing extension installation in chrome.rdf is not converted.
Severity: normal → major
What is MAS? If you mean seamonkey, there should have been no visible changes to
seamonkey at all.
(In reply to comment #3)
> What is MAS? If you mean seamonkey, there should have been no visible changes to
> seamonkey at all.

Yeah Mozilla Application Suite aka Seamonkey. Sorry, I see it like I said in bug
278534 comment 40. All menu entries from extensions like Tools -> [Extension
entry],the Adblock status bar entry and the additional preference dialog entries
 (like Mnenhy, Theme Installer) disappeared after upgrade to the 02-23-05 build.
It affected only extensions, not themes. Extensions in my profile: Adblock,
Bugmenot, Mnenhy, popupalt, themer, extuninstall. If I had time I would retest
it with an old build and new profile, install some ext. and upgrade to a current
build but ...
Firefox and Thunderbird extensions are handled correctly for quite a while now,
Seamonkey problems are bug 285155. Suggesting  WFM.
As there were no objections, resolving.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.