Closed
Bug 1087807
Opened 10 years ago
Closed 10 years ago
[e10s] canvas.drawWindow() for a chrome window doesn't draw content as well on e10s
Categories
(Core :: Graphics: Canvas2D, defect)
Core
Graphics: Canvas2D
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: harth, Unassigned)
References
Details
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.
Comment 1•10 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•10 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.
Updated•10 years ago
|
Blocks: dte10s
tracking-e10s:
--- → +
Reporter | ||
Comment 3•10 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
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•