Note that I don't plan on landing this before https://chromium-review.googlesource.com/c/chromium/src/+/7416778; I'll update things more after that lands.
| 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. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
8 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: third_party/blink/renderer/core/execution_context/security_context_init.cc
Insertions: 19, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: third_party/blink/renderer/core/permissions_policy/permissions_policy_parser.h
Insertions: 23, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: third_party/blink/renderer/core/permissions_policy/permissions_policy_test.cc
Insertions: 233, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: third_party/blink/renderer/core/permissions_policy/permissions_policy_parser.cc
Insertions: 28, Deletions: 0.
The diff is too large to show. Please review the diff.
```
Avoid bumping SecurityOrigin refcount when parsing policies
For `PermissionsPolicyParser`, the passed-in origins are referenced by
the parser context during parsing, but the parser context only lives on
the stack. In addition, the created policy does not take ownership of
the origins. While src origin is usually a newly-created origin, self
origin is typically an alias of the execution context's origin. Since no
ownership is involved, pass by const reference or const pointer and use
LIFETIME_CAPTURE_BY to ensure that the parsing context doesn't
accidentally outlive the passed-in origins.
Similarly, `IFramePolicy`'s constructor and `UpdateContainerPolicy()`
now also take the SecurityOrigin by const reference, since neither took
ownership of the SecurityOrigin, and the origin should never be null.
Also fix some style guide violations, since virtual methods should not
have default arguments.
A number of callsites were already passing `const SecurityOrigin*`, but
this implicitly converts to `scoped_refptr<const SecurityOrigin>`; those
have been fixed. Finally, rename `GetOriginForPermissionPolicy()` to
`MakeOriginForPermissionsPolicy()` to make it clear that this method can
create new origins.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |