Google Git
Sign in
chromium / chromium / src / a62d1f69f43b5f7bef92b39336a1cb416b367171
commita62d1f69f43b5f7bef92b39336a1cb416b367171[log] [tgz]
authorStefan Zager <szager@chromium.org>Tue May 02 16:43:01 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 02 16:43:01 2023
tree445288f92d624e382579c32d05313d598fd3700d
parent7c98c2c4eada44e6a6716ed19b1427a0f5db0bae [diff]
In smooth scroll test, use elapsed time to measure when scroll has ended

WPT must be designed to run on a wide variety of hardware and refresh
rates. Many of the tests have been retrofitted to accommodate test
hardware with very slow refresh rates, but some tests (like this one)
can fail when run on hardware with very *fast* refresh rates, because
500 animation frames may not be enough to reach the end of a scroll
animation.

With this change, we wait for 200 milliseconds and a minimum of 5
animation frames where the scroll offset doesn't change, with a
timeout after 8 seconds.

Bug: chromium:770028
Change-Id: I9c024cf48359dab384356285bba237fed1d57025
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4497336
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1138432}
1 file changed
tree: 445288f92d624e382579c32d05313d598fd3700d
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.