tree fcd1ba1c3e8c5e663b1aa0dd8acf9840efd8e6bd
parent 87947c86dc9c163a3193bd2ecb638292b34f8063
author Muhammad Hasan Khan <mhasank@google.com> 1652727286 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1652727286 +0000

[OOBE] Handle net::ERR_ABORTED in TOS 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

(cherry picked from commit 474177747b10308e421853181b54243b8e1ceae7)

Bug: b:232177321
Bug: b:232592745
Test: deploy to DUT, reset to OOBE flow, login and validate TOS load
Change-Id: I2a4031f19a4297ab30a93d4eaa64fb63db5f7033
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645553
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Commit-Queue: Muhammad Hasan Khan <mhasank@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1003458}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649500
Reviewed-by: Roman Sorokin <rsorokin@chromium.org>
Auto-Submit: Muhammad Hasan Khan <mhasank@chromium.org>
Cr-Commit-Position: refs/branch-heads/5060@{#22}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}