RESOLVED WORKSFORME83873
Full screen mode cannot be detected pressing F11 
https://bugs.webkit.org/show_bug.cgi?id=83873
Summary Full screen mode cannot be detected pressing F11
istvan.bender
Reported 2012-04-13 03:01:27 PDT
Using the webkit's full screen API everything goes well till the user presses F11. We don't get any full screen event pressing F11. Therefore we don't detect if we are in full screen mode, and cannot exit from full screen mode. Furthermore pressing F11 and sending document.body.webkitRequestFullScreen(); will kill all further full screen operation. See attached example.
Attachments
Full screen test page (861 bytes, text/html)
2012-04-13 03:02 PDT, istvan.bender 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
istvan.bender
Comment 1 2012-04-13 03:02:33 PDT
Created attachment 137067 [details] Full screen test page
Alexey Proskuryakov
Comment 2 2012-04-13 16:11:04 PDT
Hoe is the F11 key related to full screen? On my machine, F11 activates Expose - is this what this bug is about?
Frédéric Wang Nélar
Comment 3 2018-05-23 08:16:30 PDT
If think there are potentially two different concepts one is full screen of the browser window (depending on the system it can be F11 or Ctrl+Cmd+F) and full screen of the web content (web page, video, iframe etc). Does the spec say anything about how these two concepts are related?
Frédéric Wang Nélar
Comment 4 2026-10-09 23:15:48 PDT
Just tried again... Ctrl+Cmd+F puts the browser window in full screen, pressing "Enter fullscreen" button animates the page to put it in full screen, pressing Ctrl+Cmd+F makes both the window and page exits the fullscreen mode. If only pressing "Exit fullscreen" instead, we only exit the page fullscreen mode ; and pressing Ctrl+Cmd+F makes the window exits the fullscreen mode. If instead start pressing "Enter fullscreen", and then press Ctrl+Cmd+F, we exit the page full screen mode and don't put the window in full screen mode either. So I'm not sure I understand the bug report, but nothing looks shocking to me. I'm closing this as worksforme but feel free to reopen.
Note You need to log in before you can comment on or make changes to this bug.