[e10s] canvas.drawWindow() for a chrome window doesn't draw content as well on e10s

RESOLVED WONTFIX

Status

()

Core
Canvas: 2D
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: harth, Unassigned)

Tracking

(Blocks: 1 bug)

unspecified
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s+)

Details

(Reporter)

Description

4 years ago
Under e10s, calling canvas.drawWindow() with a chrome window will draw the chrome window but draw white/blank for any inner content. e.g. drawWindow() on the browser window will draw the tab UI, etc. but not the current web content.

The devtools eyedropper tool relies on this working.
(Reporter)

Updated

4 years ago
Blocks: 1040653

Comment 1

4 years ago
Hmm, this might be interesting to fix. We don't want sync drawWindow calls from the parent. We do have support for remote thumbnailing now through PageThumbs, maybe dev tools can work with that instead?

Comment 2

4 years ago
For the e10s version of the responsive mode , I take a screenshot in the content process and send it back to the main process. See bug 1067145.
Blocks: 875871
tracking-e10s: --- → +
(Reporter)

Comment 3

4 years ago
I went the route in comment 2. Seems like it would be hard or bad to implement synchronously, so I'm wontfixing.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.