Closed
Bug 1325349
Opened 8 years ago
Closed 8 years ago
use ImageLayer's imageContainer directly in WebRenderImageLayer
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox53 | --- | affected |
People
(Reporter: jerry, Assigned: jerry)
References
Details
Attachments
(1 file)
ImageLayer already has a ImageContainer, we don't need another one in WebRenderImagelayer.
|
Assignee | |
Comment 1•8 years ago
|
||
Attachment #8821132 -
Flags: review?(sotaro.ikeda.g)
|
||
Comment 2•8 years ago
|
||
mImageContainerForWR is added to handle a case that Image in ImageContainer has a TextureClient that is created by ImageBridge. If the TexutreClient exists in Image, the TextureClient could not be delivered by WebRenderBridge. Is the patch handled the case?
|
|
||
Updated•8 years ago
|
Attachment #8821132 -
Flags: review?(sotaro.ikeda.g)
|
|
Assignee | |
Comment 3•8 years ago
|
||
We already have this in WebRenderImageLayer.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•