Closed Bug 297921 Opened 20 years ago Closed 20 years ago

Clear out installed-chrome.txt during installation

Categories

(Firefox :: Installer, defect)

Product:
Firefox
Component:
Installer
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Firefox1.5

People

(Reporter: darin.moz, Assigned: benjamin)

Details

Attachments

(1 file)

Remove installed-chrome.txt (and app-chrome.manifest for good measure), rev. 1
9.99 KB, patch
darin.moz
: review+
asa
: approval-aviary1.1a2+
Details | Diff | Splinter Review 
Clear out installed-chrome.txt during installation.

Now that we do not use installed-chrome.txt for any of our built-in packages, we
probably want to go one-step further and wipe out anything else that may exist
in installed-chrome.txt after upgrading a user from firefox 1.0 to 1.1.  It's
possible that a user may have installed something using a traditional XPI (those
that use install.js) or they may have other cruft in installed-chrome.txt. 
We'll want to try to avoid problems that such chrome packages might cause when
run under Firefox 1.1.  Doing this should help minimize chances that people
report broken chrome problems that cannot be fixed by loading Firefox in safe mode.
Status: NEW → ASSIGNED
Flags: blocking1.8b3+
Target Milestone: --- → Firefox1.1
Attachment #186487 - Flags: review?(darin)
Comment on attachment 186487 [details] [diff] [review]
Remove installed-chrome.txt (and app-chrome.manifest for good measure), rev. 1

nice, r=darin
Attachment #186487 - Flags: review?(darin) → review+
Attachment #186487 - Flags: approval-aviary1.1a2?
Attachment #186487 - Flags: approval-aviary1.1a2? → approval-aviary1.1a2+
Fixed on trunk for 1.8b3
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: