ExposureGuidelines: Difference between revisions

Remove "Secure contexts" and "Is this feature enabled by default in sandboxed iframes?" as they are better addressed as part of the design of a feature
(Clarify secure contexts)
(Remove "Secure contexts" and "Is this feature enabled by default in sandboxed iframes?" as they are better addressed as part of the design of a feature)
Line 31: Line 31:
* A spec issue for some change that would make it possible to test ([https://github.com/whatwg/fullscreen/issues/70 example]).
* A spec issue for some change that would make it possible to test ([https://github.com/whatwg/fullscreen/issues/70 example]).
* A Bugzilla bug for the creating web-platform-tests.
* A Bugzilla bug for the creating web-platform-tests.
''Secure contexts'': Provide justification if this feature is not restricted to secure contexts, e.g., web compatibility requires it to not be restricted. Otherwise, use "Yes" and ensure it is suitably restricted.<br>
''Is this feature enabled by default in sandboxed iframes?'' If not, is there a proposed sandbox flag to enable it? If allowed, does it preserve the invariants in terms of what sandboxed iframes can do?
</blockquote>
</blockquote>


Confirmed users
112

edits