commit | c77a1a0fe12fb2d7aaf9704ab5f9b1ca9f69b69d | [log] [tgz] |
---|---|---|
author | David Bokan <bokan@chromium.org> | Tue Jan 14 17:45:59 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 14 17:45:59 2025 |
tree | f45094f3908f7c2d3ff81acb1d215525ad18ed55 | |
parent | 9835aa3bccafbd73170015001abe4f47d3a8ebeb [diff] |
Handle changes to Glic enterprise policy at runtime This CL makes Chrome respond to changes of the Glic policy at runtime, removing or adding the tab strip button as needed. A big part of this is clearing up (and documenting) the various notions of "Glic-enabled". This CL makes sure Glic-related objects and widgets (tab notifier icons, border, etc.) are created for all browser windows/profiles where Glic could eventually be enabled; that is, those where the profile is a regular (non-incognito, non-system, non-login, etc) user profile, regardless of whether Glic is enabled in this profile _at this time_. We call such profiles "eligible". A profile is "Glic-enabled" if it is eligible and also runtime enabled by the enterprise policy. This can change at runtime so the GlicProfileConfiguration listens for changes in all eligible profiles and adds/removes the tabstrip button in existing windows as needed. Bug: 382722218 Change-Id: I5ad396086a53c84ec17a6dfb48f38acfaf3299d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6165743 Reviewed-by: Anthony Cui <cuianthony@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Dana Fried <dfried@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1406173}
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.