New issue
Advanced search Search tips
Starred by 2 users

Issue metadata

Status: Fixed
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment

Issue 643234: LBS extension launches chrome window in the background when redirecting (in gmail - "Test this link")

Reported by, Sep 1 2016 Project Member

Issue description

Version: 52.0.2743.116
OS: Windows 10

Chrome browser + Legacy Browser Support (Chrome extension and IE addon) 

After updating to LBS 4.6, clicking "Test this link" while adding a URL/composing on Gmail WEB UI opens a new Chrome browser which does not get closed when a host gets redirected to IE.    (there is a chrome window launches in the background)

What steps will reproduce the problem?
1. Update Chrome extension and Internet Addon for Legacy Browser Support to 4.6 
2. Access Gmail Web UI and Create a new mail. 
3. Click on "Insert Link" at the bottom of the new mail. 
4. Add a url that redirects in Web Address field. 
5. Click on "Test this link". 

- A new Chrome browser window appears with "chrome://extension..." in the address bar, but this address disappears and it turns blank. 
- A new Internet Explorer window appears with url that redirects 

Expected output:
URL gets redirected without background chrome window.

Video if repro: 

1. At approx. 16 seconds, it opens a new Chrome browser window with "Opening in alternate browser" message 
2. At approx 18 seconds, Internet Explorer window opens 

Please note that this issue does not happen with older versions of LBS, only 4.6

Additional version information:
OS: Windows 10, Windows Server 2008 R2 
(Tested, reproducible on any Windows devices) 
Network: any network, Wi-Fi or Ethernet 
Hardware models: any Windows OS device 
Hardware SNs (if applicable): NA 
Chrome browser LBS extension verion 4.6 
Internet Explorer LBS addon version 
Chrome browser version 52.0.2743.116 m 
Internet Explorer version 11.0.9600.183376CO

Comment 1 by, Sep 2 2016

Thanks for reporting this.

Can you please tell me what was the behavior before? Did it still open a windows but then close it or did the redirection happened in a tab in the same Chrome window which then was closed?

Comment 2 by, Sep 2 2016

Project Member
Labels: Hotlist-Google

Comment 3 by, Sep 2 2016

Status: Assigned (was: Untriaged)
has owner -> assigned

Comment 4 by, Sep 27 2016

We cannot guarantee if this issue was reproducible in the older versions.

Comment 5 by, Sep 29 2016

I could reproduce this. 

The issue is that the current logic of keeping the last Chrome tab open does not reflect the fact that there might be multiple Chrome windows open. Also it considers popup windows as proper Chrome windows and then navigates the single page there which is the "last" one to the new-tab-page. 

In the next release this will be fixed to not consider popup-s as proper windows and close them independently of the keep_last_chrome_tab policy.

If you rather wish that Chrome is closed when a navigation is redirected to IE today you can set the "Keep last Chrome tab open" to disabled today and this will also cause the bad test link behavior to go away.

Comment 6 by, Oct 12 2016

Is there any info regarding the next release such as a release date?

Comment 7 by, Nov 7 2016

Hi there,

is there any update on this issue?
Thank you :)

Comment 8 by, Nov 7 2016


we don't have a date for the next release of LBS yet. I will update this bug once we have such date.

This issue will be fixed in the next release for sure though.

Comment 9 by, Dec 12 2016

@pastarmovj, Any idea when the new release will be ? Do we have a date or is still in the works ?

Comment 10 by, Jan 13 2017

Status: Fixed (was: Assigned)
This bug has been fixed. Now LBS will not leave popups open after transtion anymore regardless of the state of the "Keep last Chrome tab open" policy. Also in case of multiple windows left even when the policy is active only the last tab of the last window will be left not all windows with one tab.

The fix will appear either as a minor update to LBS v.4 or as part of the large next release planned for later this year. The fix will be uploaded as minor version update to the beta channel in the next 24hours though.

Sign in to add a comment