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

Issue 779588 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 19
Cc:
rkalavakuntla@chromium.org
█ susanjuniab@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Creating window from extension popup freezes popup UI until the window is closed.

Reported by donald.b...@gmail.com, Oct 30 2017 
Chrome Version       : 61.0.3163.100
OS Version: 10.0
URLs (if applicable) :
Other browsers tested: None

What steps will reproduce the problem?
1. Load the unpacked extension in the attached file.
2. Install the extension in Chrome.
3. Click the browserAction icon to open the popup.
4. Click the radio buttons to show that the UI is responsive.
5. Click the Start button to create a window (tested with both normal and popup windows).
6. Click the radio buttons to show that the popup UI is still responsive.
7. Close the popup.
8. Reopen the popup.
9. Click the Start button and radio buttons which are now unresponsive and do not respond to clicks.
10. Close the window opened in step 5.
11. Click the start and radio buttons which are still unresponsive and do not respond to clicks.
12. Close the popup.
13. Open the popup.
14. Click the radio buttons to show that the popup UI is again responsive.


What is the expected result?

After opening the window in step 5 and reopening the popup in step 8 the popup should remain responsive to mouse clicks on the start and radio buttons.

What happens instead of that?

After opening the window in step 5 and reopening the popup in step 8 the popup becomes unresponsive to mouse clicks on the start and radio buttons.

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

Loading the popup in step 8 after the window is created in step 5 is quicker than opening the popup in steps 3 and 13 (in steps 3 and 13 a wait icon is seen, but not in step 8). I suspect that the popup window is not being recreated in step 8. Could there be a reference from the opened window back to the popup?

Tested also with the window created with focused set to false.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
window creation test.zip
3.2 KB Download

Comment 1 by rkalavakuntla@chromium.org, Oct 31 2017

Cc: rkalavakuntla@chromium.org
Labels: Needs-Milestone Needs-Feedback
Tested the issue on Win-10 using chrome reported version #61.0.3163.100, latest stable #62.0.3202.75 and canary #64.0.3254.0 and unable to reproduce the issue as per comment #0.

Steps that included to reproduce the issue are:
1. Loaded the unpacked extension in the attached file.
2. Installed the extension in Chrome.
3. Clicked the browserAction icon to open the popup.
4. Clicked the radio buttons to show that the UI is responsive.
5. Clicked the Start button to create a window (tested with both normal and popup windows).
6. Clicked the radio buttons to show that the popup UI is still responsive.
7. Closed the popup.
8. Reopened the popup.
9. Clicked the Start button and radio buttons which are now responsive and do not respond to clicks.
 
In step 9: After clicking the Start button and radio buttons, they are still responsive and responded to clicks as expected.

donald.bryant.rich@ :Please find the attached screencast and let us know if anything is missed from our end. 
And also try to recheck the issue by upgrading your browser to latest stable #62.0.3202.75 and let us know your observations if the issue still persists.

Thanks..!
779588.webm
4.3 MB View Download

Comment 2 by donald.b...@gmail.com, Oct 31 2017 

Thank you. After watching your screen capture I did further testing. The problem does not appear if Chrome and the window opened from the extension are on the same monitor (or perhaps if both are on the first monitor) as in your test (as shown by the window appearing over the Chrome window). The problem does appear if Chrome is opened on the second monitor and the window opened from the extension is opened on the first (or a different?) monitor (as shown in the second screen capture where the window is not seen to open over the Chrome window). Please see the two attached screen captures. 

I also tested opening the window from Chrome running on the second monitor and then moving the window to the second monitor. Even after moving the window the controls in the popup are unresponsive.

These recording were made today using the latest version (Version 62.0.3202.75 (Official Build) (64-bit)).

Please tell me if there is a way to create the window on a specified monitor (there does not seem to be a parameter for this in chrome.windows.create()). If there is a way, I will test with Chrome on the first monitor and opening the window on the second monitor.
Chrome Window Bug Same Monitor.webm
4.2 MB View Download
Chrome Window Bug Second Monitor.webm
4.5 MB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 31 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rkalavakuntla@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by susanjuniab@chromium.org, Nov 3 2017

Cc: susanjuniab@chromium.org
Labels: -Type-Bug -Pri-3 hasbisect-per-revision M-64 Pri-1 Type-Bug-Regression
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on Windows 10 on latest stable 62.0.3202.75 and Canary 64.0.3257.0	with the steps mentioned in comment #2.
Unable to reproduce this issue on Windows 7, Mac OS 10.12.6 and Ubuntu 14.04.

Bisect Information:
=====================
Good build: 61.0.3113.0 (Revision-475195)
Bad Build : 61.0.3114.0 (Revision-475229)

After running the per-revision bisect script, below is the changelog URL.
Change Log URL: 
===============
https://chromium.googlesource.com/chromium/src/+log/7dd8d45f5ab70e09fe32710186f9ed35f4386689..e2dcc699777d349adcb8a97ac069279977f14f2f

From the above change log the possible CL suspect is:
Reviewed-on: https://chromium-review.googlesource.com/516425

qyearsley@ Could you please check whether this issue is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!

Comment 5 by susanjuniab@chromium.org, Nov 3 2017

Owner: qyearsley@google.com

Comment 6 by qyears...@chromium.org, Nov 3 2017

Owner: ----
Status: Available (was: Assigned)
Wrong change -- that change couldn't affect Chrome's behavior.

Not sure who the right owner is ... I wonder if you get the same result doing another bisect?

Comment 7 by dtapu...@chromium.org, Oct 17

Labels: Needs-Feedback
Status: Untriaged (was: Available)
I tried two monitor setup for this and cannot reproduce this in Chrome 69.0.3497.100 on Windows 10. Does the issue still exist?

Comment 8 by dtapu...@chromium.org, Nov 19

Status: WontFix (was: Untriaged)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.
►

Sign in to add a comment