commit | 1fec745021be241da8c8ced6d94f87a77f930aab | [log] [tgz] |
---|---|---|
author | Jérôme Lebel <jlebel@chromium.org> | Mon May 16 20:58:37 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 16 20:58:37 2022 |
tree | 03a4e85f1c28d4ffefb56aaf75092d2257bd1300 | |
parent | a0c5e79e8918e1b97a0f91063b7159c6db8052ab [diff] |
[iOS] Unify the notion of “managed” for Welcome and Sign-in Cherry pick of crrev.com/c/3613769 for M103. (with crrev.com/c/3649665 to fix a typo). The Sign-in screen had a more restrictive view than the Welcome screen of what it meant to be “managed”. I unify them by using a unique class method to determine whether the app is managed. I do not know whether it makes a difference in real use with real managed device, as it is not clear whether the difference between both way to test whether a device is managed actually exists outside of test settings. However, this will at least ensure that testers can test correctly. Change-Id: Ib542cdd454fd576a4d45d2438070687002eb86df Fixed: 1315636 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3650438 Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/branch-heads/5060@{#32} Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
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.