New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allowfullscreen attribute for iframes #2291

Open
mhartoft opened this Issue Feb 9, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@mhartoft

mhartoft commented Feb 9, 2016

The mere existence of mozallowfullscreen and webkitallowfullscreen suggests that allowfullscreen comes with compatibility issues. I blindly just use all 3, while also suppressing my inner fear that IE doesn't support any of it.

@Malvoz

This comment has been minimized.

Show comment
Hide comment
@Malvoz

Malvoz Jul 26, 2018

Contributor

Please note that Feature-Policy introduced the allow attribute. The attributes below (including the allowfullscreen as suggested here) are considered legacy attributes and have equivalent allow directives. The legacy attributes will be ignored when allow is present (and supported).

  • allowfullscreen attribute is equivalent to feature-policy directive: allow="fullscreen"
  • allowpaymentrequest attribute is equivalent to feature-policy directive: allow="payment"
  • allowusermedia attribute is equivalent to feature-policy directive: allow="camera microphone"
Contributor

Malvoz commented Jul 26, 2018

Please note that Feature-Policy introduced the allow attribute. The attributes below (including the allowfullscreen as suggested here) are considered legacy attributes and have equivalent allow directives. The legacy attributes will be ignored when allow is present (and supported).

  • allowfullscreen attribute is equivalent to feature-policy directive: allow="fullscreen"
  • allowpaymentrequest attribute is equivalent to feature-policy directive: allow="payment"
  • allowusermedia attribute is equivalent to feature-policy directive: allow="camera microphone"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment