Closed
Bug 272798
Opened 20 years ago
Closed 20 years ago
Theme manager has problems with pngs.
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: tyler, Assigned: bugs)
Details
Attachments
(1 file, 1 obsolete file)
|
917 bytes,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Using FireFox 1.0 with the "Install New Theme 0.3" extension, I was working on a custom theme. When I replaced the icon.png (an only the icon.png) in an working theme.jar, it caused the theme to fail to install properly. This behaviour seems to happen with transparent pngs and pngs with a dpi of 96 and a comment (the output from Photoshop 7.0). Opening the icon.png file in the GIMP 2.0 and re-saving as a png without any modifications and replacing the icon.png in the theme.jar with the new version caused the theme to install properly with the new icon. The GIMP reset the dpi to 72 and stripped the comment. When I try to install the theme.jar with the Photoshop or transparent icon.png the theme either briefly appears on the theme list and then disappears, or it is listed with what appears to be a default theme icon, no information and a no preview.png file message in the preview window. Reproducible: Always Steps to Reproduce: 1. Install the "Install New Theme 0.3" extension so you can install local themes. 2. Create a PNG with Photoshop 7.0 or a transparent png. 3. Replace the icon.png in any theme jar file with the new png. 4. Install the theme Actual Results: The theme failed to install correctly, either disappearing from the window or failing to display any of the informations specified in the contents.rdf file(s). Expected Results: Installed the theme with new icon displayed. I have 4 cash ids that may be related to this problem or potentially to errors in my rdf. They occured while I was trying to get my theme to work: TB2296016Q, TB2293665H, TB2293338W, TB2292697W
| Reporter | ||
Comment 1•20 years ago
|
||
This is a PNG that has a gamma channel, if you replace the icon.png in a theme package with it, the theme will no longer install correctly.
Comment 2•20 years ago
|
||
Seems to work for me. I took Pinball 0.9.9.1, replaced icon.png inside with saved icon.png (5548 bytes) and it installed ok. Are you sure you attached correct image? Can you load the "bad" image in Firefox by typing its URL in location bar? I drag and dropped the jar file instead of using the extension.
| Reporter | ||
Comment 3•20 years ago
|
||
D'oh, wrong file.
Attachment #167649 -
Attachment is obsolete: true
| Reporter | ||
Comment 4•20 years ago
|
||
Testing on my home computer (Windows 2000 with Firefox 1.0) gives me slightly different behaviour with Qute and the second PNG. Qute installs on every second try. The first time it briefly shows up and then disappears, the second time it doesn't disappear (Drag'n'Drop or via "Install New Theme 0.4"). Also trying Noia 2.0 with a transparent PNG and got the same behaviour.
Comment 5•20 years ago
|
||
Couldn't reproduce with Pinball. The file is 917 bytes long now.
Comment 6•20 years ago
|
||
This was probably due to the zip reader cache holding the jar file open when installing the theme and thereby preventing the install. The icon and preview images were read directly from the jar file and I have reproduced this bug previously. Since the patch for bug 291946 landed I have not been able to reproduce this behavior and I was unable to reproduce this behavior with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050604 Firefox/1.0+ ID:2005060409 Also of note is bug 295013 which fixes a similar issue. Tyler - can you verify this is fixed with a current nightly?
Comment 7•20 years ago
|
||
I am very sure this is now WFM after the patches for the bugs I mentioned landed.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•