Google Git
Sign in
chromium / chromium / src / e319b4681c62d18350ecee8d9b4ae673e15cd073
commite319b4681c62d18350ecee8d9b4ae673e15cd073[log] [tgz]
authorMuhammad Hasan Khan <mhasank@google.com>Mon May 23 18:24:40 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 23 18:24:40 2022
tree8f1b6e38842e2155fba6e301dc813a5070537b56
parente14a425e1518523f88eadf23d7dcf7b059a0e36b [diff]
[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}
2 files changed
tree: 8f1b6e38842e2155fba6e301dc813a5070537b56
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.