NEW108230
History API breaks Fullscreen API 
https://bugs.webkit.org/show_bug.cgi?id=108230
Summary History API breaks Fullscreen API
Adam
Reported 2013-01-29 14:45:44 PST
I don't know if it's entirely WebKit bug, or Chrome related bug, but: Under following url: http://adam.sobaniec.com/Sandbox/Fullscreen When following steps will be performed: 1. Enter fullscreen mode 2. Run an event that uses History API (pushState) and modifies URL 3. In Chrome fullscreen mode will automatically close. What went wrong? When history.pushState() is being executed in fullscreen mode, and the url is being modified, browser should not exit fullscreen mode
Attachments
Add attachment proposed patch, testcase, etc.
Jer Noble
Comment 1 2013-01-30 12:39:10 PST
That (pushState) probably results in the didStartProvisionalLoad callback being called.
Jer Noble
Comment 2 2013-01-30 12:42:32 PST
In Safari, I can reproduce this problem, but only when using the navigation buttons (i.e. Back, Forward) brings the state back to another page. This may be a difference between WebKit1 and WebKit2, or between the Chromium implementation of full screen vs. Apple/Mac.
Frédéric Wang Nélar
Comment 3 2026-10-12 09:00:53 PDT
I'm trying like this on Safari 27.0.1 on macOS: 1. Go to https://webkit.org/ 2. Go to https://people.igalia.com/fwang/fullscreen.html 3. Press the "toggle fullscreen video" button. 4. Press Cmd + left arrow to go back. webkit.org/ is rendered as a blank page. 5. Press Cmd + right arrow to go forward, this does not go back to people.igalia.com Firefox and Chrome properly goes back / forward. (In reply to Adam from comment #0) > browser should not exit fullscreen mode I'm not sure whether this last statement is correct, but the history should not be broken in any case and we should still be able to do go back / forward. See also bug 312575 which seems to have similar issue.
Note You need to log in before you can comment on or make changes to this bug.