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

Issue 733251 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression
LBS



Sign in to add a comment

[LBS] Legacy Browse support redirection open URL in new IE window on background

Reported by pha...@csas.cz, Jun 14 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Update LBS to version 4.7.0.0 (from 3.0.0.0)
2. Set IE to open links from other programs in a new window 
3. Run Chrome and navigate to URL which is configured to be redirected to IE. URL is redirected to IE.

What is the expected behavior?
New IE window should be opened in foreground as active window.

What went wrong?
URL is redirected, but Chrome remains the active window and new IE window is opened minimized.

Did this work before? Yes LBS 3.0.0.0 - I don't have install sources for any version between

Chrome version: 59.0.3071.86  Channel: n/a
OS Version: 10.0
Flash Version: 

IE is correctly opened (brought to) foreground, when IE is set to open links from other programs in a new tab in the current window.

I also noticed that after update to LBS 4.7.0.0, the IE setting "open links from other programs in:" is changed from "A new window" to "A new tab in the current window" for all users.
 

Comment 1 by mmenke@chromium.org, Jun 14 2017

Components: Platform>Extensions
Don't suppose anyone on the extensions team knows where to file bugs about "Legacy Browser Support" (Which looks to be an official Google Chrome plugin?)
Cc: pbomm...@chromium.org rdevlin....@chromium.org
Labels: pre-stable-59.0.3071.86 M-59
cc'ing rdevlin.cronin@ for further triage on the bug.
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
Tested this issue on Windows 10 with chrome #58.0.3029.110 with LBS 4.7.0.0

These are the steps followed
1.Configured "https://yahoo.com" in "Hosts to open in the alternative browser" policy in LBS
2.On client machine on navigating to the https://yahoo.com

Observed IE browser as the active screen and chrome was in the background.

Attaching the screen-cast for reference.

phampl@ could you look into it and let us know your observations.


Issue 733251.mp4
3.9 MB View Download
Issue 733251.png
149 KB View Download
Owner: pastarmovj@chromium.org
Status: Assigned (was: Unconfirmed)
I think maybe pastarmovj@ has worked on LBS?
Cc: blumberg@chromium.org
Components: -Platform>Extensions
Thanks I am the owner of LBS so the bug ended up in the right place :)
The setting whether IE opens links in new Tabs or Windows is actually outside of the control of LBS. What did change in LBS is that this setting is now respected since v.4.1 I think. Please see if setting the IE policy for tabs vs. windows solves your problem and if it still misbehaves reply back to this bug.

Comment 7 by pha...@csas.cz, Jun 20 2017

The main problem is in different behavior of LBS when IE is set to open links in "new tab in the current window" or "new window". Below is a video covering both scenarios. When IE is set to "new tab in the current window", the redirected page pops to the foreground. When IE is set to "new window", the redirected page is opened on the background.

https://youtu.be/zC-B-Gc1Qi0


Labels: -M-59 -pre-stable-59.0.3071.86 LBS
Summary: [LBS] Legacy Browse support redirection open URL in new IE window on background (was: Legacy Browse support redirection open URL in new IE window on background)
Thanks for the good visual explanation! I see what you mean now. We will try to get the fix in the next LBS version if possible. If not it will be in the first refresh to the upcoming 5 release.
This still happens in version 5 with chrome version 61.0.3163.79.


Yes 5 was already branched off when we started this. I expect to upload a new beta release in the upcoming 2 weeks which should contain that fix as well. I will ping this bug when it is ready for testing. 
Thank you for your patience.
Status: Started (was: Assigned)
Fix is in ready should be available in the next minor release in a couple of weeks on the beta channel.
Status: Fixed (was: Started)
This fix is in the beta channel (v5.1) now for about a week. Marking as fixed. The stable release will happen at the end of November.

Sign in to add a comment