Closed Bug 976533 Opened 6 years ago Closed 6 years ago
[CSS Blending] An element which has mix-blend-mode other than normal does not blend if it has a child which also has mix-blend-mode set
590 bytes, text/html
35.89 KB, text/html
4.18 KB, patch
|Details | Diff | Splinter Review|
1.98 KB, patch
|Details | Diff | Splinter Review|
39.67 KB, image/jpeg
No description provided.
Summary: [CSS Blending] mix-blend-mode does not work when the element that has mix-blend-mode set has a child element which also has mix-blend-mode set → [CSS Blending] An element which has mix-blend-mode other than normal does not blend if it has a child which also has mix-blend-mode set
(In reply to Horia Iosif Olaru from comment #0) > Sorry for the lack of description. I accidentally pressed the return key... If we have an element with mix-blend-mode set to something other than normal, and this element has a child that also has a mix-blend-mode set, the child element blends correctly with the parent element. The parent element is no longer blended however.
Test case that reproduces the issue. The 'intermediate' class element does not blend with the 'parent' class element, and it should. When removing the mix-blend-mode property from the 'child' class, the 'intermediate' class element will blend with the parent.
Adding a paint dump. This issue seems to happen because of the way mix-blend-mode is implemented. When creating the display list for an element wich creates a stacking context, and also has a child wich has mix-blend-mode, the whole list for the stacking context creating element is wrapped in a BlendContainer item. This BlendContainer isolates blending, among other things. The parent element creates a stacking context because of having mix-blend-mode set, and is represented by a MixBlendMode item. Because this element also has a child element with mix-blend-mode set, and create a stacking context, it will also be wrapped in a BlendContainer item. In the attached dump, one ca see that the BlendContainer wraps the parent element MixBlendMode item. Since the BlendContainer isolates blending, it will likely also isolate its own MixBlendMode element. This seems like an unfortunate edge case of the BlendContainer based implementation, that might be solvable by making the MixBlendMode item alway wrap the BlendContainer. I need to test this though.
This issue depends on bug 952051 because, just like in bug 947121, an element with mix-blend-mode which in turn has a mix-blend-mode child, has an associated container layer that uses a surface.
Depends on: 952051
Comment on attachment 8382735 [details] [diff] [review] mix-blend-mode-nested.patch Review of attachment 8382735 [details] [diff] [review]: ----------------------------------------------------------------- ::: layout/generic/nsFrame.cpp @@ +2024,5 @@ > } > } > > + /* If adding both a nsDisplayBlendContainer and a nsDisplayMixBlendMode to the > + * same list, the nsDisplayBlendContainer should be added first. This only trailing whitespace
Attachment #8382735 - Flags: review?(roc) → review+
Attachment #8382736 - Flags: review?(roc) → review+
Removed trailing whitespace.
Attachment #8382735 - Attachment is obsolete: true
Try run (including patches that fix the dependency bug 952051): https://tbpl.mozilla.org/?tree=Try&rev=e245c118706e
Assignee: nobody → olaru
OS: Mac OS X → All
Hardware: x86 → All
Flags: in-testsuite? → in-testsuite+
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
I've tested this fix using the following environment: FF 32 Build Id:20140602072051 OS: Win 7 x64 But the bug doesn't seem to be fixed. I've attached a printscreen. It seems that the intermediate class has no effect.
I'm unable to reproduce the problem. What do you see here: http://codepen.io/adobe/pen/ac11eea3fe4b0ba55aa7e667afa51a3a
Sorry I got back so late to your request. There are 3 rectangles of different colors on a yellow background. I think it's working correctly now.
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.