Chrome Legacy Browser Support (LBS) - Unable to set Chrome Arguments
Reported by
rainer...@gmail.com,
Aug 31
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36 Steps to reproduce the problem: 1. Enable and configure LBS "Chrome Arguments" through group policy, for example set the value to --new-window 2. Navigate to Chrome://Policy What is the expected behavior? The chrome arguments policy would be populated. What went wrong? The policy is not set. WebStore page: https://chrome.google.com/webstore/detail/legacy-browser-support/heildphpnddilhkemkielfhnkaagiabh Did this work before? N/A Chrome version: 68.0.3440.75 Channel: n/a OS Version: Flash Version: The extension's schema.json file has a typo, it uses the term chrome_parameters instead of chrome_arguments. Changing it to chrome_arguments resolves this bug.
,
Sep 4
rainern.w@ Thanks for the issue. Able to reproduce the issue on Windows 10, Mac OS 10.13.3 and Ubuntu 17.10 on the latest Stable 68.0.3440.106 and the latest Canary 71.0.3541.0 by following the given steps above. Attached is the screen shot for reference. This is a Non-Regression issue as this is observed from M-60 chrome builds. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Sep 7
pastarmovj@, are you the right owner for this?
,
Sep 9
Yes, lbs is me. :) Thanks for the hint. This has slipped unnoticed for quite some time! :) A minor update for LBS is planned to happen very soon and this will certainly be part of it!
,
Sep 13
Expect the fix on the beta channel as v5.5 by the end of this week.
,
Sep 13
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by viswa.karala@chromium.org
, Sep 2