commit | 8480ea6ad3d8ca4d67ae99d3eb3e45445d89607a | [log] [tgz] |
---|---|---|
author | Muhammad Hasan Khan <mhasank@google.com> | Mon May 16 18:54:46 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 16 18:54:46 2022 |
tree | fcd1ba1c3e8c5e663b1aa0dd8acf9840efd8e6bd | |
parent | 87947c86dc9c163a3193bd2ecb638292b34f8063 [diff] |
[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}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.