| dgn | 14820ae | 2016-04-08 13:15:40 | [diff] [blame] | 1 | # WebView Policies |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | WebView supports a subset of Chrome's policies, that can be set via the |
| 6 | [App Restrictions][1] mechanism. They are read on the embedder app itself rather |
| 7 | than from a centralized location. That gives administrator more flexibility and |
| 8 | granularity, but to apply a global policy, it has to be set separately |
| 9 | on each app. |
| 10 | |
| 11 | The policies will be applied to WebViews used inside the targeted apps without |
| 12 | having to modify the apps themselves. No special WebView APIs have been added |
| 13 | to expose policy information. If developers want to change their app's behavior |
| 14 | depending on that, they can [read them][2] as they have access to the |
| 15 | App Restrictions. |
| 16 | |
| 17 | Please see the [Policy List on chromium.org][2] for more information and the |
| 18 | list of supported policies. |
| 19 | |
| xiaoyin.l | 1003c0b | 2016-12-06 02:51:17 | [diff] [blame] | 20 | [3]: https://developer.android.com/training/enterprise/work-policy-ctrl.html#apply_restrictions |
| 21 | [1]: https://developer.android.com/training/enterprise/app-restrictions.html |
| Felipe Andrade | 239aaf3c | 2019-09-11 12:31:58 | [diff] [blame] | 22 | [2]: https://cloud.google.com/docs/chrome-enterprise/policies |
