New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 834302 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Bug

Blocked on:
issue 712213
issue 690520



Sign in to add a comment

Feature policy should track opaque origins across renderers and the browser data structures

Project Member Reported by iclell...@chromium.org, Apr 18 2018

Issue description

Feature policies can be applied to frames whose documents have opaque origins, but the origins themselves cannot be referred to consistently in different renderer processes, or between renderers and the browser. As a result, it is not possible to craft a feature policy that targets a specific opaque origin.

We should change this, once we have the ability to identify specific opaque origin objects.
 

Comment 1 by creis@chromium.org, Apr 18 2018

Cc: creis@chromium.org mkwst@chromium.org nasko@chromium.org dcheng@chromium.org
Thanks!  For context, see comment 16 of  issue 690520 .  (This bug is about the second step.)

Design doc:
https://docs.google.com/document/d/1m3FYAKRjdz5wEclkT_qdZXSINIG4eK54jUo5L90LSDU/edit#heading=h.6xz05leuhwuj

Comment 2 by cha...@chromium.org, Jan 18 (4 days ago)

Ian, is still to be addressed?

Comment 3 by iclell...@chromium.org, Yesterday (44 hours ago)

Yes, I think there is still one more piece -- sandboxed frames with an allowlist referencing 'src' currently match *any* origin loaded in the frame, since we're only tracking a single boolean in that case. We should store the actual initial opauqe origin, but it will also involve either knowing that origin in advance of document loading, or else updating the container policy on first document load.

Comment 4 by nasko@chromium.org, Today (17 hours ago)

I've recently added tracking of precursor origin for opaque origins in  issue 882053 , which can potentially be helpful here. Feel free to reach out if you have any questions.

Sign in to add a comment