Obsolete
Status Update
Comments
la...@gmail.com <la...@gmail.com> #2
[Comment Deleted]
ji...@chromium.org <ji...@chromium.org> #3
[Empty comment from Monorail migration]
[Monorail components: -Blink Blink>Fullscreen]
[Monorail components: -Blink Blink>Fullscreen]
br...@gmail.com <br...@gmail.com> #4
I'm seeing the same problem using the Escape key to exit full screen on OSX. It's worse than that: after forcing to exit full screen, future full screen requests no longer work, even after reloading the page.
ea...@chromium.org <ea...@chromium.org> #5
Unable to reproduce, please re-test in beta or canary.
la...@gmail.com <la...@gmail.com> #6
Tested with Version 54.0.2827.0 canary (64-bit)
I am able to reproduce it.
I am able to reproduce it.
sh...@chromium.org <sh...@chromium.org> #7
Thank you for providing more feedback. Adding requester "eae@chromium.org" for another review and adding "Needs-Review" label for tracking.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
For more details visit
ch...@chromium.org <ch...@chromium.org> #9
This would be really nice bug to fix. I have wanted it repeatedly in the past
few weeks to fullscreen video without clicking on the fullscreen icon on the page.
AFAIK this bug blocks developers from implementing that?
foolip, any feedback?
few weeks to fullscreen video without clicking on the fullscreen icon on the page.
AFAIK this bug blocks developers from implementing that?
foolip, any feedback?
fo...@chromium.org <fo...@chromium.org> #10
This is also true of the fullscreen button in the menu next to the omnibar, right next to the zoom in/out buttons.
What this boils down to is do we want a user-triggered fullscreen mode that site cannot detect, that's simply resizing the window? This issue could be solved by having just one fullscreen mode, but that would also mean that the page could call document.exitFullscreen(). Maybe that's fine, and something we could fix if it actually happens in the wild.
spqchan@, I see you're assigned to some recent "UI>Browser>FullScreen" issues, what do you think?
#3, can you file a separate issue for fullscreen no longer working?
[Monorail components: UI>Browser>FullScreen]
What this boils down to is do we want a user-triggered fullscreen mode that site cannot detect, that's simply resizing the window? This issue could be solved by having just one fullscreen mode, but that would also mean that the page could call document.exitFullscreen(). Maybe that's fine, and something we could fix if it actually happens in the wild.
spqchan@, I see you're assigned to some recent "UI>Browser>FullScreen" issues, what do you think?
#3, can you file a separate issue for fullscreen no longer working?
[Monorail components: UI>Browser>FullScreen]
sp...@chromium.org <sp...@chromium.org> #11
Keep in mind I specifically work on fullscreen on mac, not on other platforms.
AFAIK, this behavior is expected since content fullscreen is different from browser fullscreen. In this case, the API should only respond to content fullscreen. I don't think these two should be merged together.
AFAIK, this behavior is expected since content fullscreen is different from browser fullscreen. In this case, the API should only respond to content fullscreen. I don't think these two should be merged together.
fo...@chromium.org <fo...@chromium.org> #12
Hmm, so the browser fullscreen mode on Mac leaves the omnibar, for that I agree it would make no sense to fire the fullscreenchange event. I'll have to check what it looks like on Linux, if it's hiding all chrome then it's a different situation I'd say.
fo...@chromium.org <fo...@chromium.org> #13
OK, so on Linux it looks like content fullscreen, except that you have to press F11 to exit, Esc doesn't work. @spqchan, would you happen to know who works on the brwoser fullscreen mode on Linux?
cd...@chromium.org <cd...@chromium.org> #14
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
sh...@chromium.org <sh...@chromium.org> #15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
sc...@chromium.org <sc...@chromium.org> #16
[Empty comment from Monorail migration]
[Monorail components: -Blink>Fullscreen]
[Monorail components: -Blink>Fullscreen]
jm...@google.com <jm...@google.com> #17
**UI mass Triage**
We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue. Thanks!
We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue. Thanks!
jm...@google.com <jm...@google.com> #18
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #19
This issue was migrated from crbug.com/chromium/606177?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Open
2. Press F11
3.
What is the expected behavior?
"fullscreenchange" javascript event should be triggered.
What went wrong?
"fullscreenchange" javascript event is not triggered.
Did this work before? No
Chrome version: 50.0.2661.86 Channel: stable
OS Version:
Flash Version: Shockwave Flash 21.0 r0