New issue
Advanced search Search tips

Issue 826721 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Upgrading to version 65.0.3325.181 is causing problems with printing.

Reported by snarkh...@thetek.com, Mar 28 2018

Issue description

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

Steps to reproduce the problem:
1. Click the Print button on the website
2. 
3. 

What is the expected behavior?
We have a content management system, where the user can print contents on the web page. After clicking on the Print button, print preview window should open and the user can select the printing settings as they wish and print the page.

What went wrong?
When the user clicks Print button, they see a blank page in the print preview window. This started happening after we upgraded Google Chrome to the latest version, today morning.

Did this work before? Yes 64

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M65
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on chrome reported version 65.0.3325.181 using Windows-10 with steps mentioned below:
1) Launched chrome version# 65.0.3325.162 and upgraded it to 65.0.3325.181
2) Opened Wikipedia , right click on mouse and clicked on print
2) Able to see the content of the Wikipedia page in print preview page 

@Reporter: Please find the attached screen cast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging.

Thanks!

826721.mp4
5.9 MB View Download
Components: -Blink Internals>Printing
Likely  bug 819327 , which will be fixed in Chrome 66. Can you check if this is fixed in Chrome Canary, Dev, or Beta? If so, it is probably the same bug. 
Can you please tell me the release date of Chrome 66?
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 5 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
re: comment 5 - In about 12 days for Stable Channel according to: https://www.chromestatus.com/features/schedule

One can also install Chrome Beta, Chrome Dev, or Chrome Canary. All of which are currently version 66 or newer.
Labels: -Needs-Bisect M-65 Target-65 FoundIn-65
Status: Untriaged (was: Unconfirmed)
As per comment# 4, original issue:  826721  looks similar to issue:  819327  which got fixed in latest M-66 chrome, hence marking this issue:  826721  as untriaged.

As we don't have any stable refresh of M-65, and stable is moving to M-66 tentatively in two to three weeks.
NOTE: Issue seems to fixed on latest beta 66.0.3359.81. Hence removing Needs-Bisect label.
@Reporter: Please check the issue on latest beta and let us know if the issue is fixed there. You can download beta build from https://www.chromium.org/getting-involved/dev-channel.

Thanks!
Labels: Needs-Feedback
Chrome 66 is now the Stable channel release. Is this still an issue?
Status: Archived (was: Untriaged)
If this is still a problem with Chrome 66 or newer, please let us know. Closing for now.

Sign in to add a comment