exo: Advertise bug fix IDs on binding zaura_shell

Currently, fixing exo bugs for Lacros is cumbersome due to version
skew between Lacros/ash. In a single CL, we ideally want to 1) land
an exo fix and 2) land a conditional workaround in Lacros until ash
is uprevved to actually include the exo fix (see the bug for a real
world example).

To remedy this, this CL introduces a new |bug_fix| event that sends
down IDs of bug fixes present in exo when the zaura_shell is bound.
Clients (notably |ui::WaylandZAuraShell|) can listen for this event
and gate features on the presence of certain bug fixes by calling
|WaylandZAuraShell::HasBugFix(bug_id)|.

Bug: 1151508
Change-Id: Iec39e32c4b507545aaf59c0a73f3fa61f9a7e3ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568204
Commit-Queue: Brian Ho <[email protected]>
Reviewed-by: Robert Kroeger <[email protected]>
Reviewed-by: Daniele Castagna <[email protected]>
Cr-Commit-Position: refs/heads/master@{#837086}
11 files changed
tree: ef84aebfa29486c7d819605a783fbcc75727f52d
  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. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.