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

Issue 816869 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Printing in JavaScript from a opened window will show page unresponsive after 30 seconds

Reported by henning....@visma.com, Feb 27 2018

Issue description

Chrome Version       : 64.0.3282.186 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: N/A - I don't have access to Safari.
    Firefox: OK
       Edge: N/A - Print dialog doesn't show up at all

What steps will reproduce the problem?

(1) Open attached HTML file in Chrome.

(2) Click "Click me"

(3) wait 30-ish seconds (seems like moving the window may extend this time)

What is the expected result?

Nothing

What happens instead?

A message shows up telling the user that the page is unresponsive.

Please provide any additional information below. Attach a screenshot if
possible.

It doesn't show this message if I print with JavaScript on the parent window. It also doesn't show this message if the user presses Ctrl+P to print instead.

It seems that it has to be a opened child window where JavaScript calls the print method.
 
index.html
910 bytes View Download
Labels: Needs-Triage-M64
Cc: sindhu.chelamcherla@chromium.org
Components: Internals>Printing
Labels: Triaged-ET M-67 Target-67 FoundIn-67
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 64.0.3282.186 , on latest canary 67.0.3362.0 using Mac 10.13.3, Windows 10 and Ubuntu 14.04 with HTML file attached in comment#0.

Issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged.

Thanks!
Labels: OS-Linux OS-Mac OS-Windows
Owner: thestig@chromium.org
I'll take this but may not be able to get to it for a while.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Any plans for when this will get resolved? We have a customer that is affected.

Sign in to add a comment