{"action":"created","issue":{"url":"https://api.github.com/repos/WICG/feature-policy/issues/145","repository_url":"https://api.github.com/repos/WICG/feature-policy","labels_url":"https://api.github.com/repos/WICG/feature-policy/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/WICG/feature-policy/issues/145/comments","events_url":"https://api.github.com/repos/WICG/feature-policy/issues/145/events","html_url":"https://github.com/WICG/feature-policy/issues/145","id":304942277,"number":145,"title":"spec should offer a little more explanation for other specification authors","user":{"login":"dbaron","id":248721,"avatar_url":"https://avatars2.githubusercontent.com/u/248721?v=4","gravatar_id":"","url":"https://api.github.com/users/dbaron","html_url":"https://github.com/dbaron","followers_url":"https://api.github.com/users/dbaron/followers","following_url":"https://api.github.com/users/dbaron/following{/other_user}","gists_url":"https://api.github.com/users/dbaron/gists{/gist_id}","starred_url":"https://api.github.com/users/dbaron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbaron/subscriptions","organizations_url":"https://api.github.com/users/dbaron/orgs","repos_url":"https://api.github.com/users/dbaron/repos","events_url":"https://api.github.com/users/dbaron/events{/privacy}","received_events_url":"https://api.github.com/users/dbaron/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-13T21:28:39Z","updated_at":"2018-03-21T03:20:12Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"The introduction of the feature-policy specification gives a bit of advice that targets developers.  However, an important piece of this spec is going to be how it integrates with other pieces of the web, so I think the introduction (or maybe other parts of the spec) should give a bit more advice targeting specification authors.\r\n\r\nFor example, in https://github.com/mozilla/standards-positions/issues/24#issuecomment-372503880 I said:\r\n\r\n> I think it's probably most valuable to write something about how it might help the default policies for existing features to evolve over time, and how it can change the tradeoffs around the default policies for new features.\r\n\r\nand then expanded that into:\r\n\r\n> Allowing this control could allow pages that use these features (in many cases, following user consent) to prevent cross-origin subframes (which are often ads, and which often do tracking) from getting the same permission as the toplevel page. Having the control also makes it easier for future specifications to be designed so that this behavior is the default, but can be overridden in the other direction to allow the subframe to use the feature.\r\n\r\nas part of [Mozilla's position](https://mozilla.github.io/standards-positions/) on the spec."},"comment":{"url":"https://api.github.com/repos/WICG/feature-policy/issues/comments/374824103","html_url":"https://github.com/WICG/feature-policy/issues/145#issuecomment-374824103","issue_url":"https://api.github.com/repos/WICG/feature-policy/issues/145","id":374824103,"user":{"login":"clelland","id":45853,"avatar_url":"https://avatars2.githubusercontent.com/u/45853?v=4","gravatar_id":"","url":"https://api.github.com/users/clelland","html_url":"https://github.com/clelland","followers_url":"https://api.github.com/users/clelland/followers","following_url":"https://api.github.com/users/clelland/following{/other_user}","gists_url":"https://api.github.com/users/clelland/gists{/gist_id}","starred_url":"https://api.github.com/users/clelland/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/clelland/subscriptions","organizations_url":"https://api.github.com/users/clelland/orgs","repos_url":"https://api.github.com/users/clelland/repos","events_url":"https://api.github.com/users/clelland/events{/privacy}","received_events_url":"https://api.github.com/users/clelland/received_events","type":"User","site_admin":false},"created_at":"2018-03-21T03:20:12Z","updated_at":"2018-03-21T03:20:12Z","author_association":"CONTRIBUTOR","body":"> Allowing this control could allow pages that use these features (in many cases, following user consent) to prevent cross-origin subframes (which are often ads, and which often do tracking) from getting the same permission as the toplevel page. Having the control also makes it easier for future specifications to be designed so that this behavior is the default, but can be overridden in the other direction to allow the subframe to use the feature.\r\n\r\nThat's definitely one of the objectives here (well, two of the objectives -- both limiting the powers of third-party content, as well as aligning current and future specs so that more and more of the platform canbe controlled predictably), and well put -- do you mind if I make use of some of that wording? (or please feel free to suggest anything else via PR)"}}
{"actor":{"display_login":"clelland"}}