Hide ARC++ Windows with the same logical_window_id

Windows are considered one "logical window" if they are created
with the same |shelf_group_id| and |logical_window_id|.
The consequence: only one window per logical window is shown in
the shelf, the alt-tab menu, and the desk mini view.

The use case are windows across multiple screen, which are not possible
in Chrome OS. So the app creates one window per screen and marks them
as one logical window.

This is done by the |ArcAppWindowInfo|, which stores the IDs mentioned
above. It is setting the |HideInDeskMiniView| property, the
|HideInOverview| property and the new |HideInShelf| property on a
window. The AppWindowLauncherItemController pays attention to the
HideInShelf property and will not use hidden windows as
|last_active_window|s, nor return them via |GetAppMenuItems|.

When a window closes, it might have been the visible window of a
logical window, so the |AppServiceAppWindowArcTracker| checks this and
tells a different app of the same logical window to become visible.

browser_tests --gtest_filter=ArcAppLauncherBrowserTest.LogicalWindow

Test: 
Bug: b/148875131
Change-Id: Ide57ac8dbc77137d4678763bdc88806f3937c0dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207316
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Nancy Wang <nancylingwang@chromium.org>
Commit-Queue: Philipp Weiß <phweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774043}
13 files changed
tree: a226aec4f38c735c02042e20202fb20d164988f8
  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. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  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. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. ENG_REVIEW_OWNERS
  68. LICENSE
  69. LICENSE.chromium_os
  70. OWNERS
  71. PRESUBMIT.py
  72. PRESUBMIT_test.py
  73. PRESUBMIT_test_mocks.py
  74. README.md
  75. 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.

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.