[Autofill Assistant] Make script precondition timeout configurable.
Before this change, the client waited for a hardcoded duration for scripts to become available and then entered a generic error state. After this change, the timeout and action can configured by the backend. When that timeout is reached, the client executes a specific script, controls what the client does. This change also subtly modifies the time after which the client stops waiting for autostart scripts: it now stops either once it's found a script to autostart or when it's found runnable scripts to propose, instead of waiting for a script to be started. This unifies operations and avoid the unlikely but confusing case where there client would autostart a script after having proposed scripts to run. For background, see go/autobot-a2m74ux-client-errors Bug: b/125245527 Change-Id: I0bc757293ca324544f1b3d35275168ee6545c340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497073 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#637649}
Showing
This diff is collapsed.
Please register or sign in to comment