New issue
Advanced search Search tips

Issue 701613 link

Starred by 1 user
Status: Assigned
Owner:
iclell...@chromium.org
Cc:
loonyb...@chromium.org
esprehn@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Task



Sign in to add a comment

Look at moving FeaturePolicy into a component

Project Member Reported by raymes@chromium.org, Mar 15 2017 
On https://codereview.chromium.org/2738953002/ esprehn was concerned that we're going through the blink platform API to create feature policies. I think the main reason we were doing this was so that we can share code with the browser process. esprehn suggested using a component to do this instead.

I think you had explored using a component to do this, iclelland, but I can't remember what the outcome was? Do you remember?

Comment 1 by iclell...@chromium.org, Mar 15 2017

Labels: -Type-Bug OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows Type-Task
I had looked into that as a way of reconciling the differences between the code that needed to use url::Origin and the code that required blink::SecurityOrigin. I decided in the end that it wouldn't recude any of that complexity, so I went the route of putting the bulk of the code in content/common, and using the platform API and IPC to translate between the two origin classes.

In light of cr/2738953002, I'll re-examine that component plan, and see if we can detach from blink::Platform

Comment 2 by raymes@chromium.org, Mar 15 2017 

Thanks Ian!

Comment 3 by lunalu@chromium.org, Jun 12 2017

Cc: -lunalu@chromium.org loonyb...@chromium.org
►

Sign in to add a comment