| Commit-Queue | +1 |
- mike...@chromium.orgYoshisato YanagisawaWe should find a better owner than me... 😊
Updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
- chrome.*:150-
- chrome_os:150-
- android:150-Let's replace it with 149.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
- chrome.*:150-
- chrome_os:150-
- android:150-Let's replace it with 149.
I am not sure if it is feasible but let's give it a shot.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Owners-Override | +1 |
LGTM. Setting an OO bit as an emergency fix as discussed offline.
| Commit-Queue | +2 |
Add RestrictBackgroundFetchFromServiceWorkerEnabled enterprise policy
Introduces the RestrictBackgroundFetchFromServiceWorkerEnabled policy to
allow administrators to enable Background Fetch from Service Workers.
Background Fetch from Service Workers is restricted by default to
enhance security. This policy provides administrators with the ability
to explicitly allow this functionality within their organization.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
@igorr...@chromium.org Please let us know if there is any issues from the enterprise policy perspective.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
@igorr...@chromium.org Please let us know if there is any issues from the enterprise policy perspective.
Looks good overall, just a couple of comments that can be addressed in a follow-up CL (no need to merge them back to 149).
This policy controls whether background fetch requests from Service Workers are restricted. If a feature that downloads files in the background is affected, this policy may be relevant.
If this policy is set to Enabled, or left unset, the restriction is active, and background fetch requests from Service Worker contexts may be blocked.
If this policy is set to Disabled, the restriction is bypassed, allowing all Service Workers to make background fetch requests.Nit: Please add empty lines between sections / paragraphs, otherwise the text will be grouped into one block.
```suggestion
This policy controls whether background fetch requests from Service Workers are restricted. If a feature that downloads files in the background is affected, this policy may be relevant.
If this policy is set to Enabled, or left unset, the restriction is active, and background fetch requests from Service Worker contexts may be blocked.
If this policy is set to Disabled, the restriction is bypassed, allowing all Service Workers to make background fetch requests.
```
- caption: 'Default: Background Fetch restriction depends on browser defaults and field trials.'The default policy value refers to the stable value after the underlying feature is rolled out, so it should be independent of Finch trials. From the policy description it seems like the feature will behave as if enabled when the policy is unset, so I'd remove this `null` value and update the default to `true`
Comments are addressed in https://chromium-review.googlesource.com/c/chromium/src/+/7867400. Please take a look.