FR - Force updates on Chrome devices
Reported by
adm_arna...@airliquide.com,
Jun 8 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 8172.47.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Platform: Platform 8172.47.0 (Official Build) stable-channel nyan_blaze Steps to reproduce the problem: Use case: When a new Chrome OS version is released tied to some cPanel feature, it may occured errors if not all Chrome devices are in line with the newest version. What is the expected behavior? Motivation: Have an homogeneity in Chrome OS version to avoid side effect and guarantee devices security according to company security rules. What went wrong? In case of new policy applied, most of Chrome devices will experienced issues if they don't have the latest release. Did this work before? N/A Chrome version: 51.0.2704.79 Channel: stable OS Version: 8172.47.0 Flash Version: Shockwave Flash 21.0 r0 no workarounds just wait until Chrome devices triggered the new chrome os version.
,
Jun 14 2016
In addition, the new feature should be version n-1 compatible.
,
Jun 14 2016
,
Jun 14 2016
+dskaram to triage
,
Jun 16 2016
There is a policy to pin the OS version. This could be done to 95% of devices while the company trials the remaining 5% on the new version. They would then switch the others back on and they would get the update automatically. What policy broke clients?
,
Feb 28 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dchan@google.com
, Jun 14 2016