| commit | ae8d4bfcc06600e96ef458b4efb000d64d76c66c | [log] [tgz] |
|---|---|---|
| author | Dan H <harringtond@chromium.org> | Fri Aug 13 21:25:21 2021 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 13 21:25:21 2021 |
| tree | c86e79da1842e2231be59a9d115576b06894bade | |
| parent | b4366b96014bb50204027f2de23412abd88eda39 [diff] |
Revert "Reland "[TabCapture] Add BrowserTest for Enterprise Policy Scenarios"" This reverts commit 30c18ecac9b207e3e6c50df7d45de2bd56bea37c. Reason for revert: Test fails on mac-arm64-rel-tests https://ci.chromium.org/ui/p/chromium/builders/ci/mac-arm64-rel-tests/3158/test-results Original change's description: > Reland "[TabCapture] Add BrowserTest for Enterprise Policy Scenarios" > > This is a reland of 04279a88534f0567cdf46722bf505a001dddaaa1 > > Changes for Reland: Switched the construction order to ensure the > capturing tab is focused before running getDisplayMedia, and added code > to ensure the target tab is focused prior to navigation. > > Original change's description: > > [TabCapture] Add BrowserTest for Enterprise Policy Scenarios > > > > Adds Browser Tests for a couple of Enterprise Policy Scenarios: > > > > The first asserts that AppWindows can be captured via the Tab Capture > > selection list. This is guaranteed through both the use of the > > enterprise policy restricting all pages to tab capture, and the Tab > > Capture auto select by title test functionality. > > > > The second two assert that when a same origin policy is applied that the > > capture terminates if the target is navigated away from the same origin > > and continues if it is navigated within the same origin. > > > > Change-Id: I9dea36f112ea42f9928c608449ce06c307815e30 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083305 > > Commit-Queue: Alexander Cooper <alcooper@chromium.org> > > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#911448} > > Change-Id: I99ae42d680a04f637c1daed6d8088e4a62373770 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3092586 > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > Reviewed-by: Guido Urdaneta <guidou@chromium.org> > Commit-Queue: Alexander Cooper <alcooper@chromium.org> > Cr-Commit-Position: refs/heads/master@{#911793} Change-Id: Ia328097f7247be2e6564721ae49146e7e058d424 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3093710 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Dan H <harringtond@chromium.org> Owners-Override: Dan H <harringtond@chromium.org> Cr-Commit-Position: refs/heads/master@{#911891}
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.