Re: [whatwg/fullscreen] Define fullscreen in terms of feature policy (#106)

> I don't understand how 4 in https://wicg.github.io/feature-policy/#integration-with-html works.

The idea is that:

 * A document has a feature policy
 * "`allowfullscreen`" indicates the policy-controlled feature named "`fullscreen`"
 * The policy may or may not enable fullscreen for an origin, specifically the document's origin in this case.
 * By replacing step 4 (and 5 now, I think), "allowed to use" becomes:

1. If document has no browsing context, then return false.
2. If document's browsing context's active document is not document, then return false.
3. If document's browsing context is a top-level browsing context, then return true.
4. If document’s feature policy enables the feature indicated by allowattribute for the origin of document, then return true.
5. Return false.

(If FP controls the features completely, then we'd probably want to get rid of step 3 as well, since FP will also handle that case)

I've filed https://github.com/WICG/feature-policy/issues/95 to track actually making it clearer.

> How many implementers have committed to feature policy?

Chrome, certainly -- I don't know that there is any public commitment from other implementers. That does raise the question of whether it's better to include language for browsers which don't support FP, or to let PRs like this sit until there is general support. I don't know what the right answer to that is, though.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/106#issuecomment-344979968