Closed
Bug 339753
Opened 19 years ago
Closed 19 years ago
incorrect css opacity variation between object and image elements
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bugzilla-2, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
The CSS opacity property, when applied to an image element and an object element set to display the same image, render differently. That is, the opacity on the object element is somehow more transparent than the opacity on the image element. Tested using PNG images. Upon comparison to an image that had the opacity manually set via Photoshop, it appears that the opacity on the image is correct and the opacity on the object is not. Example code:
img, object {opacity: 0.3;}
[...]
<img alt="Test Image" src="object.png"/>
<object type="image/png" data="object.png"></object>
More in-depth comparison available via the supplied website demo:
http://www.angelfire.com/droid/plgaries/Opacity_Hover.html
(was formatted for another purpose; originally tested without the formatting)
Reproducible: Always
Steps to Reproduce:
1. load two images, one through an image tag, the other through an object tag
2. apply CSS opacity where opacity is /between/ 1 and 0
3. observe that the images don't look the same
Comment 1•19 years ago
|
||
I see this in 1.5.0.3 and in today's Bon Echo nightly. But I don't see this on the trunk. Both cairo and non-cairo builds have the problem corrected. So this may be something that won't be fixed in a release until 3.0. I'm not sure what bug fixed this on the trunk.
Comment 2•19 years ago
|
||
I finally got back to finding when this was fixed on the trunk. This was fixed with the landing of bug 1156 on 09-21-05. The 9-21 nightly shows the problem and the 9-22 nightly does not. That change is not eligible for 2.0. So this won't be fixed in a release until 3.0.
Setting this to WORKSFORME because it works with current trunk builds.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•