Revert "Revert "[lacros] Add wayland event for overscan insets, part 1."" This reverts commit fd66bc16a294d1206cc5274d2aa9fbf481be903f. Reason for revert: LUCI Bisection identified this CL as the culprit of a build failure. See the analysis: https://luci-bisection.appspot.com/analysis/b/8782139726712613025 Sample failed build: https://ci.chromium.org/b/8782139726712613025 If this is a false positive, please report it at https://bugs.chromium.org/p/chromium/issues/entry?comment=Analysis%3A+https%3A%2F%2Fluci-bisection.appspot.com%2Fanalysis%2Fb%2F8782139726712613025&components=Tools%3ETest%3EFindit&labels=LUCI-Bisection-Wrong%2CPri-3%2CType-Bug&status=Available&summary=Wrongly+blamed+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F4502364 Original change's description: > Revert "[lacros] Add wayland event for overscan insets, part 1." > > This reverts commit b9a92e6939ccc7fd4ef8eff0840f4b51e07dd740. > > Reason for revert: Likely cause of test failure WaylandDisplayOutputTest.DelayedSelfDestruct in Linux Chromium OS ASan LSan Tests (1) (https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20(1)/50903/overview) > > Original change's description: > > [lacros] Add wayland event for overscan insets, part 1. > > > > This change adds a new event to zaura_output_manager called > > overscan_insets, which lets the server advertise the overscan > > insets for the specified output, in physical pixels. > > > > This change implements the server and a stubbed client-side handler, > > with full implementation and usage to follow. The server's version has > > been bumped up. > > > > Bug: 1381312,1432295 > > Change-Id: I1910330599f9c21953b5b48a45b2df7fc1d6123f > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4471787 > > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > > Commit-Queue: Addison Luh <aluh@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1138595} > > Bug: 1381312,1432295 > Change-Id: Ic0ef4fe50c756c0f5b60d4c868f411056fc8165a > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4502364 > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Owners-Override: Vivian Pao <vpao@google.com> > Commit-Queue: Vivian Pao <vpao@google.com> > Cr-Commit-Position: refs/heads/main@{#1138817} > Bug: 1381312,1432295 Change-Id: I2119fa06bbbb0c92f5485045c72999ad250832cd No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4501175 Commit-Queue: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Owners-Override: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Bot-Commit: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1138818}
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.