New issue
Advanced search Search tips

Issue 692385 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 629432
Owner: ----
Closed: Aug 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Original tab can't refresh when window.print() on a new tab.

Reported by nhnhatq...@gmail.com, Feb 15 2017

Issue description

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

Steps to reproduce the problem:
1. Open a Chrome's tab (any website or even a blank page) (call it A).
2. Open Console in DevTools (F12) and enter window.open() to open a new tab (call it B).
3. On B, enter window.print() in the Console to open the print popup.
4. Comeback to A and hit F5 to refresh it.

What is the expected behavior?
A could refresh.

What went wrong?
The problem is that A cannot refresh and just shows the loading icon until the print popup on B closes.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

That problem does not occur when opening the print popup by Ctrl + P

 

Comment 1 by rtoy@chromium.org, Feb 15 2017

Cc: rtoy@chromium.org
Components: -Blink Platform>DevTools
Status: Untriaged (was: Unconfirmed)
Assuming this is a devtools issue.  If not please set the component appropriately.

Comment 2 by l...@chromium.org, Feb 15 2017

Components: -Platform>DevTools Blink>WindowDialog
Thanks for the report.  I'm able to reproduce this after closing DevTools on both tabs.  It seems related to the way that tab refresh works.
It's not the DevTools' issue. I'm developing a web app with the function of print preview. This function opens a new tab (window.open) to show the content including a print button. It executes window.print() command when a user clicks on that button. The issue happens when a user doesn't close the print popup but switch to the old tab and tries to refresh it but impossible. Therefore, he thought that my application was looping forever.
Other browsers don't have this issue because the print popup must be closed before doing anything.
If you do this 2 separated tabs which aren't relevant by the window.open command, it's fine as they can refresh normally.
Therefore, I think the window.open command creates some unknown connections between tabs so that the 1st tab understands that there is an opening print popup => it should wait.
Mergedinto: 629432
Status: Duplicate (was: Untriaged)
This is due to the fact that having a window print dialog up pauses the render process.

Sign in to add a comment