Closed
Bug 1397752
Opened 7 years ago
Closed 6 years ago
Canvas should use update_image instead of add_image
Categories
(Core :: Graphics: WebRender, enhancement, P2)
Core
Graphics: WebRender
Tracking
()
RESOLVED
DUPLICATE
of bug 1383786
Tracking | Status | |
---|---|---|
firefox56 | --- | unaffected |
firefox57 | --- | unaffected |
People
(Reporter: jrmuizel, Unassigned)
References
Details
(Whiteboard: [wr-reserve] [gfx-noted])
Currently when a canvas redraws we seem to do an add_image. It would be better if we used update.
Whiteboard: [gfx-noted]
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
status-firefox56:
--- → unaffected
status-firefox57:
--- → unaffected
Updated•7 years ago
|
Blocks: stage-wr-trains
Whiteboard: [gfx-noted] → [gfx-noted][wr-mvp][triage]
Updated•7 years ago
|
Priority: P3 → --
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted][wr-mvp][triage] → [wr-reserve] [gfx-noted]
Updated•6 years ago
|
Priority: P3 → P2
Updated•6 years ago
|
Assignee: nobody → sotaro.ikeda.g
Comment 1•6 years ago
|
||
Canvas rendering always use AsyncImagePipeline. And AsyncImagePipeline uses update_image if possible since Bug 1383786.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Assignee: sotaro.ikeda.g → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•