commit | cc7df5f223b1372d7d0a6262315d27f8c53557ed | [log] [tgz] |
---|---|---|
author | Brad Triebwasser <btriebw@chromium.org> | Thu Sep 19 20:00:01 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 19 20:00:01 2024 |
tree | 481da52587d1cc09bc134b8efe70e163e42fb0a8 | |
parent | fe446640a4cc54533ba91b2a415b3cdbfe61344b [diff] |
Reland "Remove display id in VirtualDisplayUtil::AddDisplay." This is a reland of commit 557a678e03118da342b0b98c75932901857314ee Serial numbers need to start at one on mac. A serial number of 0 was causing a crash. Original change's description: > Remove display id in VirtualDisplayUtil::AddDisplay. > > Removes the ability for callers to specify a display ID on > VirtualDisplayUtil::AddDisplay. Most platforms (except for Mac) cannot > influence the resulting display::Screen id. Instead, each virtual > display controller maintains its own internal ids. > > > Bug: 40271794 > Change-Id: If8707c2ed4ae98e59ea831f43e7fdd28797a1c3f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5840551 > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Commit-Queue: Brad Triebwasser <btriebw@chromium.org> > Reviewed-by: Mike Wasserman <msw@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1356226} Bug: 40271794 Change-Id: Ia6127882163faf7db7082570a3d77df0d07da71a Include-Ci-Only-Tests: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5870624 Reviewed-by: Mike Wasserman <msw@chromium.org> Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Brad Triebwasser <btriebw@chromium.org> Cr-Commit-Position: refs/heads/main@{#1357809}
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.