Chrome will nag 10.9 users to update, but they won't be able to |
||
Issue descriptionChrome Version: v65+ OS: MacOS 10.9 What steps will reproduce the problem? (1) On MacOS 10.9 install the latest Chrome available for that platform (v65). (2) Move your system date 3 months ahead (3) Launch Chrome What is the expected result? Chrome does not nag about being outdated. What happens instead? Chrome complains that it is outdated and the user needs to check for updates. But when the user does that, the no available updates are reported. Root cause: Chrome checks the age of its build and if it finds that the installed build is more than 12 weeks old, it shows that message. This is controllable by "OutdatedBuildDetector" feature, so we may simply disable this feature remotely through Finch experiment applicable to all macOS 10.9 users. Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Apr 23 2018
,
Jun 1 2018
Did this happen?
,
Jun 5 2018
No, not yet. I'm chatting with the Finch folks about how to properly target only 10.9. |
||
►
Sign in to add a comment |
||
Comment 1 by ellyjo...@chromium.org
, Apr 23 2018