New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767054 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Dom Inspector no longer able to capture screenshots

Reported by briancf...@gmail.com, Sep 20 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. Attempted to capture screenshot and/or full size screenshot on multiple sites.
2. Cleared cache & reset Chrome.
3. 

What is the expected behavior?
For the capture screenshot functionality to work as described/previously used.

What went wrong?
First: Full size screenshot captured nothing and displayed as only white background/foreground. Then no screenshots were captured moving forward.

Did this work before? Yes 60

Chrome version: 61.0.3163.79  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 27.0 r0
 
chromereleases.googleblog.com-(BF Work Dell).png
3.4 KB View Download
Labels: Needs-Bisect Needs-Triage-M61

Comment 2 by hdodda@chromium.org, Sep 22 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Tested the issue on windows 7 & 10 using chrome latest stable M61 #61.0.3163.100 and canary M63 #63.0.3221.0 and issue is not reproduced.

Tried screenshot with printSc button in keyboard and screenshot is fine.

Attached screencast for reference.

@briancfoor-- Could you please let us know if you are uisng any tool for screenshot and also particular  url , you are trying to capture... Please update us with your observations in latest stable.

Thanks!
767054.mp4
1.2 MB View Download
Labels: -Needs-Bisect
Removing from the bisect queue since we are not able to repro.
Status: WontFix (was: Unconfirmed)
Due to lack of user response closing this issue, please raise a new issue if you come across the similar one in any of the latest chrome versions.

Thanks!

Sign in to add a comment