Closed Bug 1479786 Opened 6 years ago Closed 5 years ago

DirectComposition based document compositor

Categories

(Core :: Graphics: WebRender, enhancement, P3)

Product:
Core
Component:
Graphics: WebRender
Version:
63 Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox63 --- affected

People

(Reporter: jrmuizel, Unassigned)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file, 3 obsolete files)

wip - DirectComposition based document composite with Document splitting
(deleted), patch
Details | Diff | Splinter Review
Once we have separate documents we want to be able to have separate DirectComposition visuals for them so we can present each document separately
Blocks: wr-intel
Depends on: document-splitting
Priority: -- → P3
Blocks: 1423324
Assignee: nobody → sotaro.ikeda.g
Whiteboard: [wr-q2][wr-may]
Blocks: wr-intel-mvp
No longer blocks: wr-intel

I think we might be able to just take a short cut and do bug 1550029 first for the mvp

Blocks: wr-intel
No longer blocks: wr-intel-mvp
Whiteboard: [wr-q2][wr-may]
Whiteboard: [wr-q3][wr-aug]

"DirectComposition based document composite with Document splitting" is enabled with the following prefs

  • gfx.webrender.split-render-roots: true
  • gfx.webrender.split-render-roots-surfaces: true

Document splitting added Popover document. The patch does not render the Popover document yet. Size of the Popover document is same to window size. When we allocate a dc layer for the Popover document, memory usage increases a lot.

Rebased.

Attachment #9089294 - Attachment is obsolete: true
Whiteboard: [wr-q3][wr-aug] → [wr-q4]
Whiteboard: [wr-q4]
No longer blocks: WR-Win-Compositing
Assignee: sotaro.ikeda.g → nobody

We're not going to do this.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: