Closed Bug 223020 Opened 22 years ago Closed 20 years ago

PNG transparency not working - inheriting the body background image instead

Categories

(Core Graveyard :: Image: Painting, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bobosola, Assigned: jdunn)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 PNG images with alpha transparency are not being rendered with properly. They are displaying a border which is being inherited from the background image applied to the Body. F5 sometimes toggles this effect on and off for one PNG but not two others. The page has valid XHTML markup & CSS. Reproducible: Always Steps to Reproduce: 1. Normal page view 2. F5 can repeatedly toggle the effect on and off for one of the PNGs but not all 3. Expected Results: Each PNG should have a transparent background. This was working OK in Moz 1.2(?) & Firebird 0.6 (Win). Now broken in Moz 1.5/Firebird 0.7 (Win). Works OK in Opera 7.2 (Win) and IE6. Screenshots here: Broken in Moz 1.5: http://homepage.ntlworld.com/bobosola/moz-1-5-PNG-bug.jpg OK in FB 0.6: http://homepage.ntlworld.com/bobosola/firebird-0-6-working-OK.jpg
WFM Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007
Looks OK in Moz 1.4/Windows 95.
Also not a problem in a current Linux trunk build....
Further: If I do a Ctrl-A or mouse select of the page, the transparent areas of the PNGs are overwritten with page text (XP, Nvidia TNT, latest driver installed). Screenshot: http://homepage.ntlworld.com/bobosola/moz-1-5-PNG-SelectAllbug.jpg
could not reproduce the problem, the page looks exactly the same in both: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031113 Firebird/0.7+ (aebrahim) XP, ATI Radeon 9000, Catalyst driver 3.8
this is most likely due to your vid card drivers. i was having the problem as well on my win2k machine running moz 1.7b until today when i installed new nvidia drivers.
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/
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: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.