Revert "[PiP][Fullscreen] Add FullscreenVideoPictureInPicture feature flag for Android."

This reverts commit 114015fc10299ed363125df7ceeabbafe4e044db.

Reason for revert: 
The Suspect CL https://chromium-review.googlesource.com/q/I41bdfb0b3ebd524aaf5b920868818c820ada6115 is highly likely the cause of the crash. Please see the crash report http://crash/583804505b0352cd.
Rebase the Revert CL on top of main branch with conflicts allowed option to prevent false positive merge conflicts.

If you agree with the revert CL, please approve it and mark as Commit-Queue +2 to submit it.

More details can be found in the go/crash-revert-cls-creation.

Original change's description:
> [PiP][Fullscreen] Add FullscreenVideoPictureInPicture feature flag for Android.
> 
> This CL introduces a new feature flag `FullscreenVideoPictureInPicture`
> to control the fullscreen video Picture-in-Picture behavior on Android.
> The flag is used to guard the initialization and usage of
> `FullscreenVideoPictureInPictureController` in `ChromeActivity`.
> 
> Key changes:
> - Defined `kFullscreenVideoPictureInPicture` in media switches.
> - Exposed the flag to Java via `ChromeFeatureList`.
> - Guarded `FullscreenVideoPictureInPictureController` in `ChromeActivity`.
> - Added the flag to `chrome://flags`.
> - Added field trial testing config and metrics enums.
> - Added tests for both enabled and disabled states.
> 
> Bug: 486262122
> Change-Id: I41bdfb0b3ebd524aaf5b920868818c820ada6115
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7609066
> Commit-Queue: Phil Yan <philyan@chromium.org>
> Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
> Reviewed-by: Frank Liberato <liberato@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1593419}
> 
Crash Bug: 489715789

Change-Id: Ie5cbccacd08006fc40a6921063f0e269be5d47f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7633862
Commit-Queue: Phil Yan <philyan@chromium.org>
Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Phil Yan <philyan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1594090}
12 files changed
tree: fbbc5f77cd5154490ee666de954f1a5473eae5af
  1. .agents/
  2. .claude/
  3. .gemini/
  4. .github/
  5. agents/
  6. android_webview/
  7. apps/
  8. ash/
  9. base/
  10. build/
  11. build_overrides/
  12. buildtools/
  13. cc/
  14. chrome/
  15. chromecast/
  16. chromeos/
  17. codelabs/
  18. components/
  19. content/
  20. crypto/
  21. dbus/
  22. device/
  23. docs/
  24. extensions/
  25. fuchsia_web/
  26. gin/
  27. google_apis/
  28. gpu/
  29. headless/
  30. infra/
  31. ios/
  32. ipc/
  33. media/
  34. mojo/
  35. net/
  36. pdf/
  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. webkit/
  52. .clang-format
  53. .clang-tidy
  54. .clangd
  55. .cursorignore
  56. .geminiignore
  57. .git-blame-ignore-revs
  58. .gitallowed
  59. .gitattributes
  60. .gitignore
  61. .gitmodules
  62. .gn
  63. .mailmap
  64. .rustfmt.toml
  65. .vpython3
  66. .yapfignore
  67. ATL_OWNERS
  68. AUTHORS
  69. BUILD.gn
  70. CODE_OF_CONDUCT.md
  71. codereview.settings
  72. CPPLINT.cfg
  73. CRYPTO_OWNERS
  74. DEPS
  75. DIR_METADATA
  76. LICENSE
  77. LICENSE.chromium_os
  78. OWNERS
  79. package.json
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. SECURITY_OWNERS
  85. 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.