Issue metadata
Sign in to add a comment
|
Legacy Browser Support 5.0 - not re-directing from IE10
Reported by
technos...@gmail.com,
Oct 17 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Install LBS 4.7 and Chrome Browser 57.0.2987.110 and have LBS configured to open www.jammer.com in IE10. Enter www.yammer.com in IE and it opns correctly in Chrome. 2. Allow Google update or install manually Chrome 61.0.3163.100 and LBS 5.0 then enter www.yammer.com in IE10 - it opens in a new tab of IE10 and no longer in Chrome. 3. Uninstall LBS 5.0 and re-install LBS 4.7 - opening www.yammer.com from IE10 now opens correctly in Chrome. What is the expected behavior? with LBS 5.0 installed and configured with www.yammer.com to open in Alternative browser (Chrome). Visit URL in IE10 and expect it to open in Chrome. What went wrong? with LBS 5.0 installed and configured with www.yammer.com to open in Alternative browser (Chrome). Visit URL in IE10 and it opens the URL in the current IE10 tab, not Chrome. Did this work before? Yes LBS 4.7 Chrome version: 61.0.3163.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: LBS is configured by GPO in our environment, all was working fine with Chrome 57.* and LBS 4.7.
,
Oct 17 2017
,
Oct 18 2017
Julian: you worked on similar problem in the past crbug.com/436422
,
Oct 18 2017
Solved : Thanks for the link back to the older logged issue, it led us to a fix. The devices where this wasn't working had the IE10 options 'Enable Third Party Browser Extensions' deselected on them by a GPO. If we select that and restart the IE session, LBS then redirects correctly to Chrome. I can't explain why this all worked with v4.7 of LBS though, was it something new / fixed in 5.0 maybe? Many thanks.
,
Oct 18 2017
No idea, but I'm glad it worked for you! :-)
,
Oct 19 2017
Thanks still for reporting this - it will help others that might experience the same issue. To be honest I can't tell why this was not needed for 4.7 when they both are third-party in that sense. I guess it is a change in IE which grandfathered known add-ins and the upgrade made it appear as a new one and thus needed the explicit approval. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by technos...@gmail.com
, Oct 17 2017