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

Missing chrome in extension hangs Firefox

RESOLVED WORKSFORME

Status

()

Toolkit
Add-ons Manager
RESOLVED WORKSFORME
13 years ago
9 years ago

People

(Reporter: Timothy Humphrey, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

1.7 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [asaP2])

Attachments

(2 attachments)

1.39 KB, application/x-zip-compressed
Details
1.41 KB, application/x-zip-compressed
Details
(Reporter)

Description

13 years ago
If an updated extension ceases to use a chrome overlay file and doesn't 
include it in the jar file for the new release Firefox will hang.  What 
appears to be the problem is that version 1 of the extension specifies a xul 
file, when the extension is updated to version 2 Firefox will add a reference 
to new xul overlay files in the 
chrome\overlayinfo\browser\content\overlays.rdf file in the Profile but it 
won't remove references to xul files that were used in version 1 but not in 
version 2.  So when Firefox loads it can't find the old xul file in the new 
jar file and hangs.

I'm going to attach two versions of a test extension that demonstrates this; 
the extension just displays an alert when a window is opened.  Start with a 
clean profile and apply version 1 and then later apply version 2 on top of 
that and Firefox will hang.  If you install version 2 directly without ever 
having applied version 1 then there won't be a problem.
(Reporter)

Comment 1

13 years ago
Created attachment 169029 [details]
Version 1
(Reporter)

Comment 2

13 years ago
Created attachment 169030 [details]
Version 2

Comment 3

13 years ago
Confirmed with the following trunk build.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041216
Firefox/1.0+ (stipe)

Comment 4

13 years ago
I thought I saw it reported, but couldn't find it.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

13 years ago
Whiteboard: [asaP2]

Comment 5

13 years ago
This bug is no longer on trunk.

testextension_1.0.xpi
chrome.manifest:
overlay	chrome://browser/content/browser.xul
chrome://testextension/content/testextension.xul

testextension_1.1.xpi
chrome.manifest:
overlay	chrome://browser/content/browser.xul
chrome://testextension/content/testextension-new.xul
-> updated properly

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050403
Firefox/1.0+
I believe this was fixed by the chrome reg rewrite a while back. This is wfm as well.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.