93156 - Implement 'opacity' according to the spec (transparency)

Status: VERIFIED FIXED

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

Description

[Pierre Saslawsky]

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.

Comment 1

[Pierre Saslawsky]

*** Bug 58517 has been marked as a duplicate of this bug. ***

Comment 2

[Markus Hübner]

What are the current plans - intending to further develop -moz-opacity or 
focus on being according to the spec?

Comment 3

[louis bennett]

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.)

Comment 4

[Brett Donald]

The CSS3 Color module has now moved to Candidate Recommendation. Can we proceed 
to fix this bug now?

Comment 5

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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).

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Taking to cover the renaming, which should wait until it works on Mac.

Comment 7

[alanjstr]

adding transparency synonym

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Attachment: patch

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");

Comment 9

[Robert O'Callahan (:roc) (email my personal email if necessary)]

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.

Comment 10

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 142085 [details] [diff] [review]
patch

r=bzbarsky.

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Fix checked in to trunk, 2004-02-23 22:48 / 23:37 -0800.

Comment 12

[Zibi Braniecki [:zbraniecki][:gandalf]]

Robert, is there any bug related to that problem?

Comment 13

[Hixie (not reading bugmail)]

+           attribute DOMString        Opacity;

Shouldn't that be 'opacity'? (lowercase)

Comment 14

[Gérard Talbot]

Folks, I believe it should be "opacity" and not "Opacity", like this:

ElemRef.style.opacity = strValue;

My 2 cents

Comment 15

[Robert O'Callahan (:roc) (email my personal email if necessary)]

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.

Comment 16

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Case corrected.