Closed
Bug 286688
Opened 20 years ago
Closed 20 years ago
CSS3 opacity not working correctly for images.
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: daniel.oconnor, Unassigned)
Details
Attachments
(1 file)
|
754 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
See testcase. The image is rendered with the parent container's opacity.
Reproducible: Always
Steps to Reproduce:
1. Create a div with an id
2. Set div's opacity < 1
3. Create an image inside of the div
4. Use css to set image's opacity to 1
Actual Results:
Image's opacity is not set.
Expected Results:
Image's opacity is set.
| Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
This is INVALID.
http://www.w3.org/TR/css3-color/#transparency
Note that it is not inherited and can therefore not be overwritten. You should
use rgba() or so which is not supported atm.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•20 years ago
|
||
(In reply to comment #2)
> This is INVALID.
>
> http://www.w3.org/TR/css3-color/#transparency
>
> Note that it is not inherited and can therefore not be overwritten. You should
> use rgba() or so which is not supported atm.
Are there any other current, implemented workarounds? Otherwise we can see
undesireable effects where a page background is displayed partly through a
content div, but images in the content div still retain the see through effect -
it's quite an unsettling effect.
Failing that, where's the best place to address comments in regards to css3 and
get clarification?
Comment 4•20 years ago
|
||
www-style@w3.org is the place to ask clarification about W3C working drafts.
Note however that others have done so before and the WG will most likely point
you to the rgba() and hsla() values.
You need to log in
before you can comment on or make changes to this bug.
Description
•