Reviewer source(s):
pma...@chromium.org, vsavu is from context(chrome/enterprise/gwsq/enterprise-policy-review.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
If this policy is set to Enabled or left unset, Web Workers created from data: URLs will have a unique opaque origin. This is aligned with the HTML specification and improves security.Please include some background information. Ideally a link to more documentation for end users.
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/enterprise/description_guidelines.md
This policy is intended to be temporary and will be removed in milestone 157.Is the default values for this policy changing with its introduction?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
If this policy is set to Enabled or left unset, Web Workers created from data: URLs will have a unique opaque origin. This is aligned with the HTML specification and improves security.Please include some background information. Ideally a link to more documentation for end users.
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/enterprise/description_guidelines.md
I've updated the description to include a comprehensive Background paragraph that explains what a data: URL worker is and how the origin behavior is changing. Since there isn't a dedicated, admin-friendly external explainer for this specific security fix, providing the context directly inline in the policy description seemed like the most helpful approach for IT admins.
This policy is intended to be temporary and will be removed in milestone 157.Is the default values for this policy changing with its introduction?
Yes, Chrome's default behavior is changing (we are making the origins opaque by default), which is why this escape hatch policy is being introduced. I made sure the new description explicitly mentions that Chrome is changing its default behavior to clarify this point.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
If this policy is set to Enabled or left unset, Web Workers created from data: URLs will have a unique opaque origin. This is aligned with the HTML specification and improves security.Yoshisato YanagisawaPlease include some background information. Ideally a link to more documentation for end users.
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/enterprise/description_guidelines.md
I've updated the description to include a comprehensive Background paragraph that explains what a data: URL worker is and how the origin behavior is changing. Since there isn't a dedicated, admin-friendly external explainer for this specific security fix, providing the context directly inline in the policy description seemed like the most helpful approach for IT admins.
Acknowledged
Web Workers can be created using a data: URL containing the worker's script. Previously, these workers inherited the origin of the page that created them, allowing them to access the same local storage, cookies, and other origin-bound data. To improve security and align with the HTML specification, Chrome is changing its default behavior so that workers created from data: URLs will now have a unique, opaque origin. This isolates them from the creator page's data.I think `data:`, specifically the `:` needs to be escaped or dropped from here and below.
Web Workers can be created using a data: URL containing the worker's script. Previously, these workers inherited the origin of the page that created them, allowing them to access the same local storage, cookies, and other origin-bound data. To improve security and align with the HTML specification, Chrome is changing its default behavior so that workers created from data: URLs will now have a unique, opaque origin. This isolates them from the creator page's data.Be specific about the version.
Chrome is changing its default in MXXX ...
This policy is intended to be temporary and will be removed in milestone 157.Yoshisato YanagisawaIs the default values for this policy changing with its introduction?
Yes, Chrome's default behavior is changing (we are making the origins opaque by default), which is why this escape hatch policy is being introduced. I made sure the new description explicitly mentions that Chrome is changing its default behavior to clarify this point.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
If this policy is set to Enabled or left unset, the new secure behavior is used, and Web Workers created from data: URLs will have a unique opaque origin.Should this say the "new default (more secure) behavior" ?
dynamic_refresh: falseIs it ? Will a change not affect new page loads?
- caption: 'Opaque origins for data: URLs in Web Workers are enabled'Consider adding " (new default behavior)" and " (deprecated legacy behavior)" here and below
Web Workers can be created using a data: URL containing the worker's script. Previously, these workers inherited the origin of the page that created them, allowing them to access the same local storage, cookies, and other origin-bound data. To improve security and align with the HTML specification, Chrome is changing its default behavior so that workers created from data: URLs will now have a unique, opaque origin. This isolates them from the creator page's data.Be specific about the version.
Chrome is changing its default in MXXX ...
Done
Web Workers can be created using a data: URL containing the worker's script. Previously, these workers inherited the origin of the page that created them, allowing them to access the same local storage, cookies, and other origin-bound data. To improve security and align with the HTML specification, Chrome is changing its default behavior so that workers created from data: URLs will now have a unique, opaque origin. This isolates them from the creator page's data.I think `data:`, specifically the `:` needs to be escaped or dropped from here and below.
Done
If this policy is set to Enabled or left unset, the new secure behavior is used, and Web Workers created from data: URLs will have a unique opaque origin.Should this say the "new default (more secure) behavior" ?
Done
Is it ? Will a change not affect new page loads?
You are right. Fixed.
- caption: 'Opaque origins for data: URLs in Web Workers are enabled'Consider adding " (new default behavior)" and " (deprecated legacy behavior)" here and below
| 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 |
Rakina: will you review content_browser_client.*?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |