Fix flakes for dialog pixel tests

A lot of flakes are caused by mouse interfering with the dialog and
hovering over a button or inconsistencies in focus behaviour. Usually,
dialogs have a default focused view but sometimes when running
tests in parallel, dialog is inactive and the default view isn't
focused.

This CL fixes both of those problems by 1. moving the mouse in 0x0
position and 2. clearing focus of the view before taking screenshots.
This should remove all the incosistencies and fix the flakes.

Known not fixed flakes:
1. IPH tests flake, sometimes screenshots include the anchor arrow,
sometimes not.
2. Chip test flakes on the size of screenshot taken. Sometimes it cuts
out the text and include only the icon part of the chip. First theory
was that it is caused by animation triggering and chip starting to
collapse but adding a setter to force chip to stay expanded didn't help.

Bug: 1208502
Change-Id: I626f988ae448a3a35ae57e055dcc98bcbf7dd33d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3034889
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Olesia Marukhno <olesiamarukhno@google.com>
Cr-Commit-Position: refs/heads/master@{#904917}
4 files changed
tree: 766f59e98d8a3cd25cff4e88b9a28343454491ba
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  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.