Revert "Update video picture-in-picture window title animation"

This reverts commit 247cd023ec889ccb73f505a32099cece5d6f1afb.

Reason for revert:
LUCI Bisection has identified this change as the cause of a test failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/test-analysis/b/4809414306430976

Sample build with failed test: https://ci.chromium.org/b/8709248607020047073
Affected test(s):
[ninja://chrome/test:browser_tests/PictureInPicturePixelComparisonBrowserTest.VideoPlay](https://ci.chromium.org/ui/test/chromium/ninja:%2F%2Fchrome%2Ftest:browser_tests%2FPictureInPicturePixelComparisonBrowserTest.VideoPlay?q=VHash%3A91b15303e2090379)

If this is a false positive, please report it at http://b.corp.google.com/createIssue?component=1199205&description=Analysis%3A+https%3A%2F%2Fci.chromium.org%2Fui%2Fp%2Fchromium%2Fbisection%2Ftest-analysis%2Fb%2F4809414306430976&format=PLAIN&priority=P3&title=Wrongly+blamed+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F6697443&type=BUG

Original change's description:
> Update video picture-in-picture window title animation
>
> This change updates the window animation by making the title (origin
> and favicon), together with the controls top scrim, display for 5
> seconds any time the picture-in-picture window is opened.
>
> Any interaction with the window causes the animation to revert back to
> the default implementation.
>
> Reasoning for this change available at:
> go/cme-video-pip-spoof-vulnerability-by-prompt-mimicking
>
> Bug: 397878997
> Change-Id: I2daf3d5915bc04d3a729a425e9a368e44d167a34
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6697443
> Reviewed-by: Fr <beaufort.francois@gmail.com>
> Commit-Queue: Benjamin Keen <bkeen@google.com>
> Cr-Commit-Position: refs/heads/main@{#1487129}
>

Bug: 397878997
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I56d01e621f23f87436b10b04c4591af1b42cf002
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6758830
Reviewed-by: Ming-Ying Chung <mych@chromium.org>
Commit-Queue: Ming-Ying Chung <mych@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Ming-Ying Chung <mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1487377}
3 files changed
tree: c362e65d39cec1b30fe8cb0ff7ca5d4d3888904b
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .git-blame-ignore-revs
  55. .gitallowed
  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. CPPLINT.cfg
  70. CRYPTO_OWNERS
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. SECURITY_OWNERS
  81. 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.