You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
Webapp container has a settings menu ("gears" icon), which among others allows setting the zoom level for rendering the page. This menu is only shown at the top right when "--enable-back-forward" is set, which shows the address bar and navigation buttons at the top of the window.
There are pages that do not render well at 100% zoom (depending on page design an form factor of the device). For those webapps the user should be able to access the settings menu in order to set the zoom level that suits the page. But this does not necessarily mean that the app needs navigation and a tool bar taking up display area.
Could we add a way for the user to access the settings menu (in particular the rendering zoom level) without having to set the "--enable-back-forward" option?
(Note: setting the rendering zoom level in the settings menu is not the same as using the pinch gesture on the rendered page. The zoom level in the settings menu changes the overall composition of the page, such as making parts of the page visible that were hidden or overlapped before – in particular where web pages are not made for small form factors.)
The text was updated successfully, but these errors were encountered:
the other way to get to the zoom or settings menu is via the context menu.
(long press on the page background as normally done for selecting text)
would it make sense to use the swipe up gesture for opening the WebApp settings ?
In morph-browser it opens the tab list, but that is not available for webapps.
Oh, wow, so what I asked for is already there! My apologies!
The problem then seems to be that it is not easily discoverable. The long-press gesture is very seldomly used in the UT interface at all, and in all cases I can think of there is at least something distinct to press on (a word, an icon, a button). There is just no hint at all that long-pressing the empty background could be useful in any way and that's why I simply never tried to do it.
The long-press gesture might be more familiar to Android or iOS users, but I am a UT native (UT was the first mobile OS I ever used and I won't use Android or iOS unless I'm forced to). So, yes, some swipe gesture will be much more suited to the UT experience. Or at least some hint, like a tool tip or a first-run wizard saying “long-press window background for options".
ruedigerkupper
changed the title
webapp-container: Allow accessing the settings menu independently form navigation buttons
webapp-container: Imptove settings menu independently form navigation buttons
May 28, 2021
ruedigerkupper
changed the title
webapp-container: Imptove settings menu independently form navigation buttons
webapp-container: Improve discoverability of options menu
May 28, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Webapp container has a settings menu ("gears" icon), which among others allows setting the zoom level for rendering the page. This menu is only shown at the top right when "--enable-back-forward" is set, which shows the address bar and navigation buttons at the top of the window.
There are pages that do not render well at 100% zoom (depending on page design an form factor of the device). For those webapps the user should be able to access the settings menu in order to set the zoom level that suits the page. But this does not necessarily mean that the app needs navigation and a tool bar taking up display area.
Could we add a way for the user to access the settings menu (in particular the rendering zoom level) without having to set the "--enable-back-forward" option?
(Note: setting the rendering zoom level in the settings menu is not the same as using the pinch gesture on the rendered page. The zoom level in the settings menu changes the overall composition of the page, such as making parts of the page visible that were hidden or overlapped before – in particular where web pages are not made for small form factors.)
The text was updated successfully, but these errors were encountered: