Closed Bug 922011 Opened 10 years ago Closed 10 years ago
Setting fullscreen permission is only possible for per domain basis
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 Iceweasel/24.0 (Beta/Release) Build ID: 20130920180050 Steps to reproduce: Open web-page containing html5 video tag and switch to fullscreen mode. Actual results: Each time I open such kind of page, even with the same domain name, confirmation dialog occurs again and again. In order of using fullscreen feature, I have to confirm the request each time I'm visiting youtube.com, for example. And because of that I have a large amount of entries like: r4---sn-n8v7lnez.c.youtube.com (see attached screenshot) . This happens because the permissions are set on per FQDN basis, which is weak design approach. Expected results: First, it should be possible to set permissions for wildcard domains, for example: *.youtube.com. Second, it should be possible to allow all sites to use fullscreen.
Severity: normal → major
Component: Untriaged → Webapp Runtime
Severity: major → normal
Component: Webapp Runtime → Untriaged
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Setting fullscreen permission is only poossbile for per domain basis. → Setting fullscreen permission is only possible for per domain basis
rzaah, can you set the permissions for fullscreen for YouTube in about:permissions? I was able to do that in Firefox 24 and it appears to stick for multiple visits to YouTube. I accidentally marked this bug "NEW" earlier today while I had several tabs open, by the way, and I haven't confirmed the behavior yet.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Yes, it works for all subdomains when is set by about:permissions.
Thanks rzaah! I think this looks the same as bug 760422. I'm going to mark this bug as a duplicate, and I hope the workaround helps you out for now. This may be something I can also bring to the attention of the support team so it can be a suggested workaround when people ask about fullscreen permissions on the support forums.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.