Closed
Bug 1330945
Opened 4 years ago
Closed 4 years ago
Support opacity value in WebRenderContainerLayer
Categories
(Core :: Graphics: WebRender, defect)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla54
People
(Reporter: ethlin, Assigned: ethlin)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
|
8.80 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
|
16.16 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
We don't use opacity value in the WebRenderContainerLayer for now. It will make some reftests failed. We should handle it.
Updated•4 years ago
|
Blocks: webrender-reftests
| Assignee | ||
Comment 1•4 years ago
|
||
Per bug 1322504 comment 48, we should remove random-if for the three tests [1] in this bug. [1] layout/reftests/bugs/581317-1.html , layout/reftests/bugs/650228-1.html, layout/reftests/bugs/728983-1.html
| Assignee | ||
Comment 2•4 years ago
|
||
Jeff, I want to pass the containerLayer's opacity value to webrender to make the display correct. I can create a mask layer with the opacity value for WR but it's not efficient. So originally I want to add a parameter 'opacity' for wr_dp_push_stacking_context() and make it work. Does WR support other ways to set the group opacity?
Flags: needinfo?(jmuizelaar)
Yes. It looks like this should use an Opacity filter on the stacking context.
Flags: needinfo?(jmuizelaar)
| Assignee | ||
Comment 4•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #3) > Yes. It looks like this should use an Opacity filter on the stacking context. Jeff, There is a issue about group opacity performance[1]. If I want to add opacity filter for stacking context, should I do that in issue/422 or open another issue? [1] https://github.com/servo/webrender/issues/442
Flags: needinfo?(jmuizelaar)
(In reply to Ethan Lin[:ethlin] from comment #4) > (In reply to Jeff Muizelaar [:jrmuizel] from comment #3) > > Yes. It looks like this should use an Opacity filter on the stacking context. > > Jeff, > There is a issue about group opacity performance[1]. If I want to add > opacity filter for stacking context, should I do that in issue/422 or open > another issue? > > [1] https://github.com/servo/webrender/issues/442 Stacking contexts already support an opacity filter so there shouldn't be any webrender work needed here. #442 describes a worst case performance situation. I don't think we need to worry about it here.
Flags: needinfo?(jmuizelaar)
| Assignee | ||
Comment 6•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #5) > (In reply to Ethan Lin[:ethlin] from comment #4) > > (In reply to Jeff Muizelaar [:jrmuizel] from comment #3) > > > Yes. It looks like this should use an Opacity filter on the stacking context. > > > > Jeff, > > There is a issue about group opacity performance[1]. If I want to add > > opacity filter for stacking context, should I do that in issue/422 or open > > another issue? > > > > [1] https://github.com/servo/webrender/issues/442 > > Stacking contexts already support an opacity filter so there shouldn't be > any webrender work needed here. > > #442 describes a worst case performance situation. I don't think we need to > worry about it here. Oh...I got it! I didn't notice that parameter.
| Assignee | ||
Comment 7•4 years ago
|
||
Use opacity filter in webrender.
Attachment #8829780 -
Flags: review?(jmuizelaar)
| Assignee | ||
Comment 8•4 years ago
|
||
Remove some fails-if and random-if flags and add fails-if for opacity-preserve3d-1.html which has wrong display originally.
Attachment #8829783 -
Flags: review?(jmuizelaar)
| Assignee | ||
Comment 9•4 years ago
|
||
I uploaded a wrong patch. This should be correct.
Attachment #8829780 -
Attachment is obsolete: true
Attachment #8829780 -
Flags: review?(jmuizelaar)
Attachment #8829786 -
Flags: review?(jmuizelaar)
Attachment #8829786 -
Flags: review?(jmuizelaar) → review+
Comment on attachment 8829783 [details] [diff] [review] Part2. Change reftest flags. Review of attachment 8829783 [details] [diff] [review]: ----------------------------------------------------------------- ::: layout/reftests/transform-3d/reftest.list @@ +72,5 @@ > fuzzy-if(cocoaWidget,128,9) == animate-preserve3d-parent.html animate-preserve3d-ref.html # intermittently fuzzy on Mac > fuzzy-if(cocoaWidget,128,9) == animate-preserve3d-child.html animate-preserve3d-ref.html # intermittently fuzzy on Mac > fails-if(webrender) == animate-backface-hidden.html about:blank > fails-if(webrender) == 1245450-1.html green-rect.html > +fuzzy(1,2000) fails-if == opacity-preserve3d-1.html opacity-preserve3d-1-ref.html This should probably be fails-if(webrender)
Attachment #8829783 -
Flags: review?(jmuizelaar) → review+
| Assignee | ||
Comment 11•4 years ago
|
||
try result: https://treeherder.mozilla.org/#/jobs?repo=try&revision=146e26e65e478765d83399267c9a08d66de82ca8&selectedJob=73797345
Comment 12•4 years ago
|
||
Pushed by ethlin@mozilla.com: https://hg.mozilla.org/projects/graphics/rev/da70da98ac18 Part1. Apply opacity to webrender stacking context as an opacity filter. r=jrmuizel https://hg.mozilla.org/projects/graphics/rev/5454c58fe241 Part2. Change flags of reftests after applying the opacity of WRContainerLayer. r=jrmuizel
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Target Milestone: --- → mozilla54
You need to log in
before you can comment on or make changes to this bug.
Description
•