Closed
Bug 279242
Opened 20 years ago
Closed 19 years ago
Transparency not handled correctly when setting wallpaper
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: damien, Assigned: bugs)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050104 Firefox/1.0+ (bangbang023) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050104 Firefox/1.0+ When setting a desktop wallpaper from an image with transparency all transparent areas are filled in black. While Windows BMP does not support black it should instead fill these areas with the "desktop colour" selection that is present on the "Save as wallpaper" dialog. Reproducible: Always Steps to Reproduce: 1. Go to http://www.factorycity.net/mozilla/firefox-rgb.png 2. Right-click and choose "Set as wallpaper" 3. Choose a non-black desktop colour Actual Results: The desktop is set with the correct colour and image but the image has an ugly black area where the transparency was. Expected Results: Use the chosen background colour from the "Save as wallpaper" dialog instead of using black.
Comment 1•20 years ago
|
||
The problem is with how Windows renders the png image. I believe that Internet Explorer still does not fully support png transparency. In this case, the solution I would use would be to edit the image so that transparency is not needed and save as bmp (so Active Desktop is not needed) and set that image as wallpaper.
Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1) > The problem is with how Windows renders the png image. I believe that Internet No, Firefox is creating a BMP file for Windows, specifically "%SYSTEMROOT%\Firefox Wallpaper.bmp". It therefore has nothing to do with how Windows handles PNG. [)amien
Comment 3•19 years ago
|
||
possibly related to 201198???
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 5•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•