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
Problems I have now
I understand that B and Y in most cases are associated with returning to the root/parent page--such as OS or app-based pages, like configurations and folders--but I don't believe it's associated often enough to returning to the previous page to assign them to such especially for browsing. The Meta Browser also makes it clear that the usual take is to assign it to context menus, or what a page would otherwise percieve as a right-click.
I also find myself accidentally reversing to the previous page while trying to habitually right click, and most of the websites I visit don't save any info or provide me a warning dialogue regarding leaving the page with unfinished actions when I exit them, which is really frustrating; for example, as I was writing this, I tried right-clicking on a word on this page itself and had accidentally lost all my writing.
I'm understanding that this may be a hyper-specific issue, and that I may be only one of very few who encounter this type of problem, so take it with a grain of salt, but as a common user, this is something I struggle with a lot and I have minimal doubt that there are others who are having a similar--if not the same--issue.
Proposed solution
The main and emphasized solution would simply be to re-assign the buttons to right-click when focused on a browser window and maintain their function of exiting certain windows like the keyboard or settings page to name two.
I feel the Menu button (the hamburger icon on the left controller) could retain its function of returning to the previous page as well as exiting windows as I'm not sure what else it could be used for besides something revolving the tray, such as opening the settings page, or even the menu accessible in the bottom right icon of the focused window.
Alternatives
My main problem is with the right controller, so perhaps you could maintain the Back assignment only to the Y button and fix the issue with the B button on its own, and if applicable, add a setting that mirrors the buttons so that Y is right-click and B is Back.
Another much simpler (though less effective) solution would be to lower the time it takes to hold before the context menu is brought up.
The text was updated successfully, but these errors were encountered:
I understand, and find most of your suggestions quite sensible. It's however difficult to accommodate what each user prefers. Most notably, we disabled going back using B/Y some releases ago and we got a lot of complains because many users were heavily using that. The same would happen again if we replace it by a right-click action.
That said, we could perhaps think about allowing users to map different actions to different buttons in the future.
That puts things in better clarity to me. If I had known, I would have waited a bit to submit a feature request like this one.
...And as much as I look forward to a feature like remapping, don't rush yourselves! You host a godsend of a browser already, with or without the ability to rebind.
Problems I have now
I understand that B and Y in most cases are associated with returning to the root/parent page--such as OS or app-based pages, like configurations and folders--but I don't believe it's associated often enough to returning to the previous page to assign them to such especially for browsing. The Meta Browser also makes it clear that the usual take is to assign it to context menus, or what a page would otherwise percieve as a right-click.
I also find myself accidentally reversing to the previous page while trying to habitually right click, and most of the websites I visit don't save any info or provide me a warning dialogue regarding leaving the page with unfinished actions when I exit them, which is really frustrating; for example, as I was writing this, I tried right-clicking on a word on this page itself and had accidentally lost all my writing.
I'm understanding that this may be a hyper-specific issue, and that I may be only one of very few who encounter this type of problem, so take it with a grain of salt, but as a common user, this is something I struggle with a lot and I have minimal doubt that there are others who are having a similar--if not the same--issue.
Proposed solution
The main and emphasized solution would simply be to re-assign the buttons to right-click when focused on a browser window and maintain their function of exiting certain windows like the keyboard or settings page to name two.
I feel the Menu button (the hamburger icon on the left controller) could retain its function of returning to the previous page as well as exiting windows as I'm not sure what else it could be used for besides something revolving the tray, such as opening the settings page, or even the menu accessible in the bottom right icon of the focused window.
Alternatives
My main problem is with the right controller, so perhaps you could maintain the Back assignment only to the Y button and fix the issue with the B button on its own, and if applicable, add a setting that mirrors the buttons so that Y is right-click and B is Back.
Another much simpler (though less effective) solution would be to lower the time it takes to hold before the context menu is brought up.
The text was updated successfully, but these errors were encountered: