Comments

Revert "Update Google Update COM interface definitions in google_update_idl.idl."
This reverts commit 21489fa99e78a80547d9e537f7cda88cf604e328.
Reason for revert: This broke the official builders because I did not realize that google_update_win_unittest.cc needs to be updated.
Original change's description:
> Update Google Update COM interface definitions in google_update_idl.idl.
>
> This update is required for work that is underway related to management
> of Chrome browsers for enterprise users.
>
> The google_update_idl.idl file was originally provided by the Google
> Update team. It has been modified as described in the README.chromium
> file in this CL.
>
> The change was tested with Chrome-branded builds with target_cpu set to
> "x86" and "x64". I followed these steps to make sure that this change
> does not break Chrome updates.
>
> 1. Manully set the version of Chrome in src/chrome/VERSION to a version
> prior to that which is currently served on the Dev channel.
> 2. Compile with is_chrome_branded=true and target_cpu set to one of
> "x86" or "x64".
> 3. Install the build as a Dev-channel Chrome using setup.exe on a 64-bit
> Win10 machine.
> 4. Navigate to chrome://help and make sure that the update process works
> as expected.
>
> Bug: 796270
> Change-Id: I6962b8874a7e825d41834860de0eb0fe92f5a6e3
> Reviewed-on: https://chromium-review.googlesource.com/924474
> Commit-Queue: Ali Tofigh <alito@chromium.org>
> Reviewed-by: Will Harris <wfh@chromium.org>
> Reviewed-by: Nico Weber <thakis@chromium.org>
> Reviewed-by: Greg Thompson <grt@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#539457}
TBR=thakis@chromium.org,wfh@chromium.org,grt@chromium.org,alito@chromium.org
Change-Id: Idac53b550e713d95f131cb0fe8ea189f88d89a26
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 796270
Reviewed-on: https://chromium-review.googlesource.com/939652
Reviewed-by: Ali Tofigh <alito@chromium.org>
Commit-Queue: Ali Tofigh <alito@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539549}

Comments

Reporting: Check upload permissions asynchronously
This changes the signature of the CanSendReport method so that it works
asynchronously. We need this to able to check the background sync
permission, since that can only be checked from the UI thread; we need
the async logic to pass control between the IO and UI threads in the
right way.
To reduce the number of async calls, the method has also been updated to
check several origins all at once, instead of having a single method
call for each origin. You pass in a set of origins that you'd like to
upload reports for, and the method passes back the set of origins that
you're allowed to.
Bug: 704259
Change-Id: I431b2fe1c1eb4e65cea91a86fd213e3204b852a1
Reviewed-on: https://chromium-review.googlesource.com/937566
Reviewed-by: Julia Tuttle <juliatuttle@chromium.org>
Commit-Queue: Douglas Creager <dcreager@google.com>
Cr-Commit-Position: refs/heads/master@{#539546}