There is no obvious way to exit fullscreen on a tablet when the app doesn't do it
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: ajones, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: csectype-spoof, sec-want)
Attachments
(1 file)
3.41 KB,
patch
|
jimm
:
feedback+
|
Details | Diff | Splinter Review |
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Reporter | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
![]() |
||
Comment 4•10 years ago
|
||
Comment 5•10 years ago
|
||
![]() |
||
Comment 6•10 years ago
|
||
Comment 7•10 years ago
|
||
![]() |
||
Comment 8•10 years ago
|
||
Comment 9•10 years ago
|
||
Comment 10•10 years ago
|
||
![]() |
||
Comment 11•10 years ago
|
||
![]() |
||
Comment 12•10 years ago
|
||
Comment 13•10 years ago
|
||
![]() |
||
Comment 14•10 years ago
|
||
![]() |
||
Comment 15•10 years ago
|
||
Comment 16•10 years ago
|
||
![]() |
||
Comment 17•10 years ago
|
||
Comment 18•10 years ago
|
||
Comment 19•10 years ago
|
||
Updated•10 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 20•5 years ago
|
||
Is anybody still watching this? I just made the mistake of going to fullscreen on a tablet device and had to hook up a keyboard to get out.
Chrome had the same problem, and I think they eventually caved and put a "exit fullscreen" item on the default context menu, when fullscreen is active. Seems like the least painful solution.
Comment 21•5 years ago
|
||
(In reply to James B from comment #20)
Is anybody still watching this? I just made the mistake of going to fullscreen on a tablet device and had to hook up a keyboard to get out.
Chrome had the same problem, and I think they eventually caved and put a "exit fullscreen" item on the default context menu, when fullscreen is active. Seems like the least painful solution.
Hey, based on your comment in bug 1190737 comment 1, I guess you are talking about the browser fullscreen mode (which you can enter via the fullscreen button under the hamburger menu), however, this bug is more about what should happen for a website using Fullscreen API to enter fullscreen state.
These are two different scenarios.
Normal websites supporting fullscreen also provides their own way to exit fullscreen (like YouTube's fullscreen switch button on the bottom right corner), so browser providing an escape approach is generally considered a security measure to avoid malicious (or ill-designed) websites to hold user hostage from using the browser. Thus the measure needs to always be available, but shouldn't affect the legitimate web functionalities.
Adding "exit fullscreen" to the context menu doesn't work in this scenario, because a malicious website looking on locking user's browser can easily prevent context menu from opening. Banning website from doing that under fullscreen would harm legitimate websites, which becomes a more complex problem. So while this might be a great idea for exiting the browser fullscreen mode, it is not an acceptable solution as itself in the context of this bug.
I suggest you file a separate bug with the proposed solution for the browser fullscreen mode, and that can be assessed separately.
However, given your comment in bug 1190737:
I just tried this and the problem is that when a Windows 10 device is in Tablet Mode, swiping from the top is a reserved system gesture. ... I don't think it's possible to disable these gestures. I was able to eventually activate the Firefox drag-down gesture but it took a bunch of tries.
It sounds like swiping from the top may not be a feasible solution for this issue either, so maybe we should just go with making Win button serve as an escape.
Comment 22•5 years ago
|
||
I don't currently have bandwidth working on this, unfortunately, but if everyone agrees on using Win button, then the old patch could be a good start point, and I can look into it later. ni? myself for this.
Comment 23•5 years ago
|
||
FYI the device I'm using (Surface Book 2) doesn't have a hardware Windows key on the tablet portion, and doesn't show the taskbar / Windows button while Firefox is full-screen. The system swipe-from-left gesture brings up the application switching overview (same as WIN + Tab) but I don't know if the application being switched away from gets any kind of notification.
Comment 24•5 years ago
|
||
(In reply to James B from comment #23)
FYI the device I'm using (Surface Book 2) doesn't have a hardware Windows key on the tablet portion, and doesn't show the taskbar / Windows button while Firefox is full-screen.
Oops... then I have no idea what can we do then...
The system swipe-from-left gesture brings up the application switching overview (same as WIN + Tab) but I don't know if the application being switched away from gets any kind of notification.
I suspect that we would still get a blur event or something like that, but I doubt we can make use of that, as exiting fullscreen when losing focus on desktop may be too offensive...
Comment 25•5 years ago
|
||
That's a real pickle. The OS reserves three of the four swipe gestures (from left, top, right) and I understand not wanting to overload tap / hold on the content area.
Maybe you could use this API to check if the OS is running in Tablet Mode, and only then, exit fullscreen on blur?
Comment 26•5 years ago
|
||
I just tried this and the problem is that when a Windows 10 device is in Tablet Mode, swiping from the top is a reserved system gesture. ... I don't think it's possible to disable these gestures. I was able to eventually activate the Firefox drag-down gesture but it took a bunch of tries.
It sounds like swiping from the top may not be a feasible solution for this issue either, so maybe we should just go with making Win button serve as an escape.
Hello, everybody. Swiping from top would work. The system gesture you mentioned is different. Here, swiping down from the upper edge of the screen gently would work. I made an add-on https://addons.mozilla.org/cs/firefox/addon/swipe-to-exit-fullscreen/ for this.
It works like this: a content script places a touchstart and touchend event and a background script makes the window maximized.
The paramatres are: touchstart x less than height * 0.15 (I don't know the exact value right now) and movement on x is bigger than 10. As a safety measure, touchend should be above height * 0.3 to avoid gesture collision. I've tested it and it works very well on my tablet. However, it would be much as a native feature (no limitations like going fullscreen in the pdf reader). What do you think?
Comment 27•5 years ago
|
||
*much better
Comment 28•5 years ago
|
||
I just had a follow-up thought to my previous comment. Xidorn said that exiting fullscreen on blur might be "offensive." I would broadly agree, but what if you use WMI to check how many displays are attached? Then, you could exit fullscreen on blur only when there's a single monitor. That addresses the only use case I can think of where staying fullscreen makes sense, which is to fullscreen something on one display while you're doing other work on another. If I alt-tab between a fullscreen application and another window, all on one display, and doing so makes the fullscreen application go to windowed mode, I don't think it would bother me.
Comment 29•5 years ago
|
||
Did you try my add-on?
Comment 30•5 years ago
|
||
I think that the solution here is to make a gesture. Swipe down from the top edge on the screen to see the tab bar, just like when you hover your mouse to the top of the screen on a desktop computer. Microsoft Edge does it this way.
Comment 31•5 years ago
|
||
Then click the maximize button.
Comment 32•5 years ago
|
||
(In reply to James B from comment #28)
I just had a follow-up thought to my previous comment. Xidorn said that exiting fullscreen on blur might be "offensive." I would broadly agree, but what if you use WMI to check how many displays are attached? Then, you could exit fullscreen on blur only when there's a single monitor. That addresses the only use case I can think of where staying fullscreen makes sense, which is to fullscreen something on one display while you're doing other work on another. If I alt-tab between a fullscreen application and another window, all on one display, and doing so makes the fullscreen application go to windowed mode, I don't think it would bother me.
How about switching between two full screen applications?
Comment 33•5 years ago
|
||
(In reply to petr.laskevic from comment #26)
I just tried this and the problem is that when a Windows 10 device is in Tablet Mode, swiping from the top is a reserved system gesture. ... I don't think it's possible to disable these gestures. I was able to eventually activate the Firefox drag-down gesture but it took a bunch of tries.
It sounds like swiping from the top may not be a feasible solution for this issue either, so maybe we should just go with making Win button serve as an escape.
Hello, everybody. Swiping from top would work. The system gesture you mentioned is different. Here, swiping down from the upper edge of the screen gently would work. I made an add-on https://addons.mozilla.org/cs/firefox/addon/swipe-to-exit-fullscreen/ for this.
It works like this: a content script places a touchstart and touchend event and a background script makes the window maximized.
The paramatres are: touchstart x less than height * 0.15 (I don't know the exact value right now) and movement on x is bigger than 10. As a safety measure, touchend should be above height * 0.3 to avoid gesture collision. I've tested it and it works very well on my tablet. However, it would be much as a native feature (no limitations like going fullscreen in the pdf reader). What do you think?
I meant y of course.
Comment 34•5 years ago
|
||
(In reply to petr.laskevic from comment #32)
(In reply to James B from comment #28)
If I alt-tab between a fullscreen application and another window, all on one display, and doing so makes the fullscreen application go to windowed mode, I don't think it would bother me.
How about switching between two full screen applications?
Hrm. I can't say that I've ever tried to do this, at least with a single display. I'm trying to picture a use-case. Say that I have a full-screen video player set up in the background, tab out and start a presentation (also full screen), then partway through the presentation tab back to the video. If any of those switches pushed the fullscreen application back to windowed, it doesn't seem like that would be a big problem.
Of course, I'm just one data point, maybe you'd need to do some research to see what the "common" reaction might be. I would argue, though, that if the only alternative is for the application to require a gesture to exit -- a gesture that I think hasn't been implemented in the core browser, and one that you'd have to somehow hint to the users through the UI -- then we should err on the side of exiting too frequently.
Comment 35•5 years ago
|
||
You could alt-tab between Firefox and a text editor (for example Sublime Text or Word or Writer). When you code or write documents on a laptop/tablet, you need the most vertical space, so all apps in fullscreen. One point to consider is that not all tablets have a Windows button. Also gestures are natural on tablets. You can swipe from the left side to switch between programs, swipe from the right side to view notifications in Windows 10.
For example Microsoft Edge has the gesture that I'm talking about and it works. Also there are some gestures in Firefox - pinch to zoom for example. So you can implement gestures.
Comment 36•5 years ago
|
||
Also, when a user uses the Windows button, they want to see the Start menu.
Updated•3 years ago
|
Description
•