Closed Bug 591543 Opened 14 years ago Closed 14 years ago

Flash player 10.0 + Flash Player Bug problems

Categories

(Firefox :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: josh.ho.2, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 Safari/533.4
Build Identifier: Mozilla 3.6.8

I am noticing with some flash websites that if I am running any flash player less than 10.1 and greater than 9.  That some PNG's inside flash are losing their transparency.  It appears the image was being rendered in 16bit rather than 32 bit.  It appears on most flash websites and on other browsers it appears to be fine.

Reproducible: Always

Steps to Reproduce:
1.go to a flash website with a transparent png
2.view image
3.
Actual Results:  
The image appears to be rendered in 16 bit.

Expected Results:  
The image should be displaying properly

This appears to happen on Windows machines (XP, Vista, 7) and Flash player 10.1 and less down to 9.
Please provide a URL to reproduce this issue.
Add an attachment of the partial screenshot and another one of the expected image, if possible.
does this happen with 10.1 r83? or just versions under that?
This does not happen with 10.1 r83.  I used 10.0 r42 and r44 and easily recreated the problem.
(In reply to comment #1)
> Please provide a URL to reproduce this issue.
> Add an attachment of the partial screenshot and another one of the expected
> image, if possible.

I made a temporary fix - forced the flash minimum to 10.1, but because this website was developed for 9, this bug should not happen.  I have a screenshot, would it be alright as to email you that screenshot?
You should not be using flash player 9 or 10, they have major security holes. Since this works with 10.1 r83, INVALID as it is the latest supported version. No other version is supported.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.