Closed Bug 183047 Opened 22 years ago Closed 22 years ago

excess folders in zip file (chrome folders)

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: bugzilla, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021202 Phoenix/0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021202 Phoenix/0.4

There are 166 empty folders within the zip file inside Phoenix's "chrome" folder
in the zip archive.  I have seen these excess folders in all 0.4+ nightly builds
I have used.

Reproducible: Always

Steps to Reproduce:
Summary: excess folders in zip file (crome folders) → excess folders in zip file (chrome folders)
Linux tarball has the same excess directory tree.
These folders are necessary, because all of the chrome files come in compressed
form and are decompressed during runtime. Just open one of the .jar files in the
chrome directory with a zip-utility like winzip. Marking INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Then why does phoenix work fine if I delete all 166 of these empty folders?
I don't mean to be a pest, but anyone know why, if these files are required for
phoenix to work, Phoenix works without them?
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
they're not required but it takes more work right now to remove them than is
worth it for the space savings. 
These folders are filled during runtime, as I said earlier. Marking INVALID again.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → INVALID
verifying
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.