Page.captureScreenshot doesn't give result for inactive tabs
Reported by
d.szy...@outlook.com,
Jun 17 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Create new tab with http://localhost:9222/json/new 2. Connect with websocket to given endpoint 3. Run Page.navigate with param url set to https://google.com 4. Wait for Page.loadEventFired 5. Change active tab with http://localhost:9222/json/activate/id 6. Run Page.captureScreenshot 7. Method doesn't give anything back What is the expected behavior? Page.captureScreenshot should work for inactive tabs What went wrong? Page.captureScreenshot doesn't return anything when called on inactive tab Did this work before? No Chrome version: 61.0.3133.0 Channel: canary OS Version: 10.0 Flash Version:
,
Jun 19 2017
,
Jun 19 2017
@dgozman, is this intended behavior?
,
Jun 21 2017
d.szymon@ Thanks for filing the issue. "This site can’t be reached" error displayed while accessing above provided (step 1 ) URL-http://localhost:9222/json/new on Windows 7 ,Mac 10.12.5 & Ubuntu 14.04. Are you running any web server along with this?If yes,Is there any another way to reproduce this issue using html files Please Confirm and provide the same to proceed further.
,
Jun 21 2017
Sorry, I forgot to mention that you have to start Chrome with flag --remote-debugging-port=9222 DevTools remote client can not be done in browser context due to security limitations, to reproduce it I'm using attached js file (requires packages "ws" and "fetch") with node.js
,
Jun 21 2017
Also, step 5 says "Change active tab with http://localhost:9222/json/activate/id" id should be replaced with id (from http://localhost:9222/json/list) of another page. Alternatively you can open new or change active tab with Chrome's GUI.
,
Jul 13 2017
This is a current screenshots implementation problem. We'll try to fix that, thanks for the report! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, Jun 19 2017