- From: Frédéric Wang Nélar <notifications@github.com>
- Date: Tue, 13 Oct 2026 00:00:57 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 October 2026 07:01:02 UTC
fred-wang left a comment (whatwg/fullscreen#112) > 3\. > Fullscreen inside of `<frame>` should have been forbidden by the "allowed to use" algorithm anyway. > > Right, but it [used to work](https://chromium.googlesource.com/chromium/src/+/32a059337eb1c538242091adc170c41be325443b), is all, which just means that whatever the problem is in Gecko probably doesn't apply to Chromium. I'm still fine with not allowing it. It seems this relies on Permissions-Policy, but I don't see where it forbids document in frame specifically. I was looking at this old WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=95402 And "fullscreen inside a frame" works in Safari https://people.igalia.com/fwang/webkit-bug-95402/frameset.html (served with `Permissions-Policy: fullscreen=*`) but not in Firefox or Chrome. The following "fullscreen inside an iframe" works in the three browsers: https://people.igalia.com/fwang/webkit-bug-95402/iframe.html (again served with `Permissions-Policy: fullscreen=*`). -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/issues/112#issuecomment-6140151175 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fullscreen/issues/112/6140151175@github.com>
Received on Tuesday, 13 October 2026 07:01:02 UTC