[Passwords] Use |PwdScriptsFetching| instead of |PwdChangeInSettings|
This CL fixes two issues. Both issues occurred when |PasswordChangeInSettings| was splitted into two flags |PasswordChangeInSettings| and |PasswordScriptsFetching| (https://chromium-review.googlesource.com/c/chromium/src/+/2436339), but some uses of |PasswordChangeInSettings| were not replaced with |PasswordScriptsFetching|. The change is supposed to be merged to M87 Beta. 1. The param |scripts_list_url| should be read from |PasswordScriptsFetching| Scripts fetching is controlled by |PasswordScriptsFetching| flag, not |PasswordChangeInSettings| flag. The latter might be disabled while scripts need to be fetched. So, it makes sense to read the param from the relevant feature - |PasswordScriptsFetching|. To be on the safe side, the Finch config can provide the param for both features, but the param names must be unique even in separate features. So, this CL renames the param (the param value was not used yet, so we don't need to update any configs). 2. Scripts prewarming should be controlled by |PasswordScriptsFetching|, not |PasswordChangeInSettings|. This issue was not severe and therefore it was hard to notice: even if scripts were not prefetched in advance, scripts were requested when a password check page was shown (|PasswordCheckManager::RefreshScripts|). That method used the correct flag. Bug: 1095627 Change-Id: Ibcfccf5d1348403b5dd46a15515ce4f040cc8047 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465913 Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org> Reviewed-by:Andrey Zaytsev <andzaytsev@google.com> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#816549}
Showing
Please register or sign in to comment