Closed Bug 93156 Opened 22 years ago Closed 19 years ago

Implement 'opacity' according to the spec (transparency)

Categories

(Core :: CSS Parsing and Computation, enhancement, P2)

enhancement

Tracking

()

VERIFIED FIXED
mozilla1.7beta

People

(Reporter: pierre, Assigned: dbaron)

References

()

Details

(Keywords: css3, Whiteboard: [patch])

Attachments

(1 file)

This bug is extracted from bug 58517.  Dbaron wrote:

The '-moz-opacity' property doesn't match the recommendation for 'opacity':

'-moz-opacity' is inherited and applies only to any painting done for the element 
(at least it did the last time I checked)

'opacity' is not inherited and should apply to the entire subtree drawn by the
element

The former is totally wrong and only works reasonably in certain simple cases.

--------------

I looked into the way we use '-moz-opacity' and it doesn't seem that we are 
already taking advantage of the difference between the two definitions. So, 
unlike what I wrote in bug 58517 [2001-07-17 16:31], the way to go would be to 
fix '-moz-opacity' when we can, and rename it to 'opacity' as soon as the spec 
becomes a recommendation.
*** Bug 58517 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Severity: normal → enhancement
Summary: [rfe] Implement 'opacity' according to the spec → Implement 'opacity' according to the spec
What are the current plans - intending to further develop -moz-opacity or 
focus on being according to the spec?
URL of [now published] spec should be: http://www.w3.org/TR/css3-color/#transparency

(sorry, i don't have the privs to add it myself.)
The CSS3 Color module has now moved to Candidate Recommendation. Can we proceed 
to fix this bug now?
This is basically a duplicate of bug 212366, but this can cover renaming
'-moz-opacity' to 'opacity' while still supporting '-moz-opacity' (at least for
a while).
Depends on: 212366
Taking to cover the renaming, which should wait until it works on Mac.
Assignee: kmcclusk → dbaron
Status: ASSIGNED → NEW
Component: GFX → Style System (CSS)
QA Contact: chrispetersen → ian
adding transparency synonym
Summary: Implement 'opacity' according to the spec → Implement 'opacity' according to the spec (transparency)
Depends on: 228441
Keywords: css3
Attached patch patchSplinter Review
I've tested that each of the following:

javascript:void(alert(document.body.style.Opacity));
javascript:void(alert(document.body.style.MozOpacity));

work both without any of the following and after each of them:

javascript:void(document.body.setAttribute("style", "opacity: 0.8"));
javascript:void(document.body.setAttribute("style", "-moz-opacity: 0.6"));
javascript:void(document.body.style.Opacity = "0.2");
javascript:void(document.body.style.MozOpacity = "0.4");
Attachment #142085 - Flags: superreview?(roc)
Attachment #142085 - Flags: review?(bzbarsky)
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [patch]
Target Milestone: Future → mozilla1.7beta
Comment on attachment 142085 [details] [diff] [review]
patch

It doesn't quite work according to spec yet (e.g., multiple boxes for the same
element aren't collapsed into the same opacity group) but I agree it's good
enough.
Attachment #142085 - Flags: superreview?(roc) → superreview+
Comment on attachment 142085 [details] [diff] [review]
patch

r=bzbarsky.
Attachment #142085 - Flags: review?(bzbarsky) → review+
Fix checked in to trunk, 2004-02-23 22:48 / 23:37 -0800.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Robert, is there any bug related to that problem?
+           attribute DOMString        Opacity;

Shouldn't that be 'opacity'? (lowercase)
Folks, I believe it should be "opacity" and not "Opacity", like this:

ElemRef.style.opacity = strValue;

My 2 cents
oops yeah, missed that. It should be lowercase.

Zbigniew, I don't think there's a bug on that. I'm planning to fix it as part of
some significant painting changes that I'm working on.
Case corrected.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.