
Changes references to the old policy documentation, replacing by the new policy list page. The patterns for the old and new URLs can be found on the bug description. Bug: 987706 Change-Id: I53b020af2499731b159987f1995da943bf160ddb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1780836 Commit-Queue: Felipe Andrade <fsandrade@chromium.org> Reviewed-by: Maksim Ivanov <emaxx@chromium.org> Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by: Matt Mueller <mattm@chromium.org> Reviewed-by: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#695578}
23 lines
1018 B
Markdown
23 lines
1018 B
Markdown
# WebView Policies
|
|
|
|
## Overview
|
|
|
|
WebView supports a subset of Chrome's policies, that can be set via the
|
|
[App Restrictions][1] mechanism. They are read on the embedder app itself rather
|
|
than from a centralized location. That gives administrator more flexibility and
|
|
granularity, but to apply a global policy, it has to be set separately
|
|
on each app.
|
|
|
|
The policies will be applied to WebViews used inside the targeted apps without
|
|
having to modify the apps themselves. No special WebView APIs have been added
|
|
to expose policy information. If developers want to change their app's behavior
|
|
depending on that, they can [read them][2] as they have access to the
|
|
App Restrictions.
|
|
|
|
Please see the [Policy List on chromium.org][2] for more information and the
|
|
list of supported policies.
|
|
|
|
[3]: https://developer.android.com/training/enterprise/work-policy-ctrl.html#apply_restrictions
|
|
[1]: https://developer.android.com/training/enterprise/app-restrictions.html
|
|
[2]: https://cloud.google.com/docs/chrome-enterprise/policies
|