[ios] Fix overscroll actions animation

The animation that happens as the overscroll actions view is going away
appeared to be especially abrupt and glitchy on the NTP. After some
investigation, it appears that the "header inset" (the content offset
in the parent ScrollView where the overscroll view is placed) was being
used incorrectly in this animation. On the NTP, the top of the parent
ScrollView's content is not offset zero, it is somewhere in the
neighborhood of -550px because the top of the feed is always offset
zero. This is wildly different than a "normal" WebKit view and resulted
in a very short glitchy animation.

In both the NTP and WebKit view cases, the added offset was causing the
animation to not really complete. For example, as the offset nears zero
the reload icon should rotate CCW as it disappears and the New Tab and
Close icons slide towards the center. This part of the animation was
lost (completely on the NTP, partially on WebKit views) because of the
offset and it really just slid up off screen and faded out. This offset
may have been added with the introduction of the notched iPhone which
resulted in an additional offset at the top of the screen.

Additionally, the parent view was not animating its slide back up into
position as it appeared the code was trying to do. This was fixed by
changing the setContentOffset:animated: to instead use a UIView
animation which included both the contentOffset and the contentInset,
resulting in a smooth slide back up into position.

Existing animation:
https://drive.google.com/file/d/1miStOXWKHbALJP8-00KnZbtzJhL5PQiT/view?usp=sharing

Fixed animation:
https://drive.google.com/file/d/1KIv_Y0rwEl0UGRxrZrwzscKvnAu6fC36/view?usp=sharing

Fixed: 1502218
Change-Id: Ia163697fcc9190f983be1226d976928ceed42b4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5105628
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Commit-Queue: Scott Yoder <scottyoder@google.com>
Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1235315}
2 files changed
tree: 1a2aaa6c3063990d9f4f0b8d50ce4bd83e807aaa
  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_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  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.