tree 8f1b6e38842e2155fba6e301dc813a5070537b56
parent e14a425e1518523f88eadf23d7dcf7b059a0e36b
author Muhammad Hasan Khan <mhasank@google.com> 1653330280 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1653330280 +0000

[OOBE] Handle net::ERR_ABORTED in assistant webview

When a webview is reloading, net::ERR_ABORTED error is thrown to stop
the previous request and start a new one.

Currently we show the error screen without checking the kind of error
which results in error being shown if we retry or the system attempts to
load/refresh the UI automatically soon after initiating it earlier.

This is a temporary fix. A more comprehensive fix would require that we
keep track of current state of request and only initiate a new one when
previous one has completed or failed with an error. A similar approach
is used by oobe_eula.js

Bug: b:232177321
Bug: b:232592745
Test: tast run DUT arc.OobeArc.vm
Change-Id: I779cd36fbcd56da5af71ebba4c8eab81334f942a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649501
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Muhammad Hasan Khan <mhasank@chromium.org>
Cr-Commit-Position: refs/branch-heads/5060@{#188}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}