Receive powerwash after update from update engine
Currently, chrome deals with powerwash after an update (e.g. on channel
downgrade) itself, from computing whether it should happen, to actually
issuing a powerwash which is never executed because the update engine
takes care of it.
After this change and the corresponding changes in the update engine,
chrome will rely on the update engine sending a flag indicating whether
a powerwash will happen after the update.
The system notifications will be addressed in a separate CL because
adapting the code there also requires properly dealing with the
rollback flag.
Depends on https://crrev.com/c/2187672
Bug: 2187671
Change-Id: I2aa7024fb7978c21e6396e366f9876d42a72e873
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2187635
Commit-Queue: Miriam Polzer <[email protected]>
Reviewed-by: Esmael Elmoslimany <[email protected]>
Reviewed-by: Kyle Horimoto <[email protected]>
Cr-Commit-Position: refs/heads/master@{#771503}
diff --git a/chrome/browser/ui/webui/help/version_updater_basic.cc b/chrome/browser/ui/webui/help/version_updater_basic.cc
index 93e3f41..2a4c334 100644
--- a/chrome/browser/ui/webui/help/version_updater_basic.cc
+++ b/chrome/browser/ui/webui/help/version_updater_basic.cc
@@ -13,7 +13,8 @@
const Status status = UpgradeDetector::GetInstance()->notify_upgrade()
? NEARLY_UPDATED
: DISABLED;
- status_callback.Run(status, 0, false, std::string(), 0, base::string16());
+ status_callback.Run(status, 0, false, false, std::string(), 0,
+ base::string16());
}
VersionUpdater* VersionUpdater::Create(content::WebContents* web_contents) {
