Closed
Bug 1694547
Opened 4 years ago
Closed 4 years ago
WebRender capture sequence parameters should be set by JS
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
88 Branch
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: jimb, Assigned: jimb)
Details
Attachments
(1 file)
nsIDOMWindowUtils should let JavaScript choose the capture path and flags for capturing WebRender frame sequences.
Assignee | ||
Comment 1•4 years ago
|
||
This patch is plumbing to get a path and a flags word through from the content
process to the graphics process, to pass to wr_api_start_capture_sequence
.
Updated•4 years ago
|
Assignee: nobody → jimb
Status: NEW → ASSIGNED
Pushed by jblandy@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c8ab839b716f
Let chrome JavaScript control WebRender capture sequence parameters. r=jrmuizel
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•