Feature #1072
closed
hold current tab to access page config
Added by ask low about 1 year ago.
Updated 7 months ago.
Description
This is my idea, to access the flooring page settings:
https://github.com/hoyon/mpv-mpris/assets/117489882/8c4a1996-703a-439b-afed-a7e5c99781c9
to appear when the current page tab is holded. The above page settings is temporary, & will revert to defaults when the tab is closed anyways.
My idea, is that accessing the webpage config is a two tap process (menu > page), which this implementation will ease that into one tap (hold). And the hold behaviour doesn't interrupt users workflow in any forms.
- Assignee set to Soren Stoutner
I'm not sure I understand your request. Specifically, I can you explain what is the difficulty with the current implementation?
It's not a big difficulty btw. I frequently started changing user agents due to browser incompatibility, disabling dark webview due to some missing css sections or fonts, etc.
I noticed that accessing page inside menu, felt pretty much repetitive.
If there is a way to implement holding the current tab in tabbar to assign any function, is that possible to assign page section to it ?
It's just a UX improvement. Nothing huge.
I personally find that if I am doing much with the user agent I almost always create a Domain Settings. Are you saying that you are often changing the user agent for web pages you only visit once or otherwise aren't creating a Domain Settings for?
I often changing UA, not for a specific website, but for different ones. Like reading different news articles. Hence do not wish to create domain settings for them.
Same goes with dark webview mode. Although I feel like turning into light mode completely in the future, as many websites look broken with the inversion of background & foreground. I'm still using it for the hope that I can access disabling it frequently with ease.
- Status changed from New to Feedback
I personally feel that, for the amount of use it typically gets, the User Agent options item is in the correct place. Moving it up to the main menu would take too much screen real estate there for its use case. However, I will leave this feature request open for a while. If a significant number of users request that it be moved to a more prominent location, I might reconsider.
Not specifically moving it into the tabbar hold. You can keep it in menu as it is & assign the menu list as a shortcut for tabbar holding.
After holding the current tab, just spawn the page menu list, which'll help access the temporary toggles must faster.
I'm not even sure if there is a programatic way to open a subpage of the options menu. Everything can be accomplished by adding enough custom code, but I generally like to stick with standard Android tools unless there is a compelling reason to do something different.
https://www.stoutner.com/privacy-browser-design-guidelines/
- Priority changed from 3.x to 4.x
Then it might not be worth if you wanna stick to the standards. As you say that it may require custom code, I'm now hesitant for such UX changes.
I think you should close this in favour of #1145 because I'm expecting current tab hold to spawn history dialog.
- Status changed from Feedback to Closed
Also available in: Atom
PDF