-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I need a multi-touch option for touch environments. #511
Comments
It looks as duplicate for #357 Please explain your idea with three-finger tap. How it would may work |
For example, touching the screen with three fingers simultaneously could bring up the pop-up that usually appears when clicking the extension icon, or maybe even directly translate the current webpage. In the case of the 'Translate Web Pages' extension, when you touch the screen with three fingers, a pop-up appears asking if you want to translate the current webpage. The 'Immersive translate' extension, on the other hand, has a feature where it translates the webpage when you touch it with three fingers. |
@Angsimosaurus sounds absolutely disgusting for me as for user, since this behaviour will affect on my interaction with site, and may destroy my experience in case site have some features with three finger gestures. This problem is common for low quality translators like Immersive translate who interfere in page content too much |
Do you also find the popup approach like TWP undesirable? I think that since this feature can be toggled on and off by those who need it, it allows only those who need it to use it and doesn't interfere with the experience. This is also based on my own experience where using Immersive Translate didn't hinder my web browsing. |
@Angsimosaurus No, i think that's fine. I see your concern and totally agreed that current behaviour must be improved. But i agree that feature proposed by you, may be opt-in feature for users who used to this way. The feature would be disabled by default, and can be enabled manually in settings if user sure it will works fine for their use cases. Let's talk about details. I have next questions to you, to understand the ideal implementation.
|
|
All the features work great on PC, but trying them out on Android felt like a lengthy process: 'hamburger menu -> Linguist -> Translate page & auto-translate current site'. It would be nice to have an option for touch environments, such as displaying the translation options with a three-finger tap or translating the current page directly.
The text was updated successfully, but these errors were encountered: