commit | 5f2f9067af2e2bab89354ec958044f53fce41ba1 | [log] [tgz] |
---|---|---|
author | Rubin Deliallisi <rubindl@chromium.org> | Thu Nov 14 15:37:04 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 14 15:37:04 2024 |
tree | 091051b9c3fa27c6b5d48378d5fb6e6e15788f77 | |
parent | ef906799e2a3ceb884a1d7719a9d46746688bfb0 [diff] |
Reland "[iOS][TM] Require reauthentication for the full lock setting" This is a reland of commit 8b433b87861606fdb1a81de539e3c9a6bc1fa99c Original change's description: > [iOS][TM] Require reauthentication for the full lock setting > > - Require reauthentication when transitioning to/from the Incognito > lock Reauth setting. This matches the existing behavior of the switch > for this setting. > - Do not update the preferences when the user clicks on the already > setting again. > - Add unit tests to fully test the behavior of the IncognitoLock VC. > > Bug: 370804664 > Change-Id: I962187749e6dee16c4e01959b4bdc2d197c571ef > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6012359 > Reviewed-by: Gauthier Ambard <gambard@chromium.org> > Commit-Queue: Rubin Deliallisi <rubindl@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1382220} Bug: 370804664 Change-Id: I530d9d4e9210ff2220fe6063aca9a6fdc3c79e1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6018567 Commit-Queue: Rubin Deliallisi <rubindl@chromium.org> Reviewed-by: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/main@{#1383002}
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.