From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5) Gecko/20011011 BuildID: 2001101117 Mozilla comes packaged with many JAR-compressed archives of resource files. Sometimes users, testers, or developers need to modify the contents of these files to test new functionality. Mozilla should be able to automatically use either the JAR file or its' decompressed equivalent without requiring additional manual manipulation by the user. Reproducible: Always Steps to Reproduce: 1. Decompress one of the JAR files installed by Mozilla (e.g., toolkit.jar) 2. Start the Mozilla application. Actual Results: The "Select Profile" dialog displayed only its' Title Bar, and no Menu Bar items were displayed. Mozilla was, thus, unusable. Expected Results: Mozilla should have used the toolkit/ directory instead of the toolkit.jar file. At the very minimum, deleting the Component Registry file should allow this to happen. Even that should not be required, though.
Assignee: pchen → hyatt
Futuring. All platforms support building without using jars, so developers can always use that option.
Target Milestone: --- → Future
In general I'd like to see more emphasis on Mozilla's end-user configurabity. For me, that single aspect is more important than any other, and I would not use another browser unless it provided a similar level of configurability. The ability to leave exploded the jar files I've edited would be a significant step in that direction. It'd be cool if I could even edit the various interface description files from within Mozilla itself, but first thing's first.
It appears Mozilla has long had this functionality. Using PatchMaker's pmuj command, Mozilla can be run with both Jarred and unJarred chrome present (though not unJarred alone). Resolving WFM.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
mass-verifying WorksForMe bugs. reopen only if this bug is still a problem with a *recent trunk build*. mail search string for bugspam: AchilleaMillefolium
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.