Skip to content
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

Open
Angsimosaurus opened this issue Sep 23, 2024 · 6 comments
Open

I need a multi-touch option for touch environments. #511

Angsimosaurus opened this issue Sep 23, 2024 · 6 comments
Labels
enhancement New feature or request features Only for important features for implement

Comments

@Angsimosaurus
Copy link

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.

@vitonsky vitonsky added enhancement New feature or request questions Further information is requested labels Sep 23, 2024
@vitonsky
Copy link
Collaborator

It looks as duplicate for #357

Please explain your idea with three-finger tap. How it would may work

@Angsimosaurus
Copy link
Author

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.

@vitonsky
Copy link
Collaborator

vitonsky commented Sep 23, 2024

@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

@Angsimosaurus
Copy link
Author

Angsimosaurus commented Sep 23, 2024

@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.

@vitonsky
Copy link
Collaborator

@Angsimosaurus No, i think that's fine. I see your concern and totally agreed that current behaviour must be improved.
Currently i prefer the solution with a float panel on top/down of screen that will have most used controls. This solution looks most minimal invasive and suitable for most users. Is this approach used in TWP too, right?

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.

  • What exactly features you need on mobile device to be available in quick access?
  • What features could be placed in floating popup at bottom of viewport?
  • What exactly should happens when user touch the screen with 3 fingers? You can also record and demonstrate here current behaviour in other extensions, that is close to ideal by your opinion.

@Angsimosaurus
Copy link
Author

@Angsimosaurus No, i think that's fine. I see your concern and totally agreed that current behaviour must be improved. Currently i prefer the solution with a float panel on top/down of screen that will have most used controls. This solution looks most minimal invasive and suitable for most users. Is this approach used in TWP too, right?

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.

  • What exactly features you need on mobile device to be available in quick access?
  • What features could be placed in floating popup at bottom of viewport?
  • What exactly should happens when user touch the screen with 3 fingers? You can also record and demonstrate here current behaviour in other extensions, that is close to ideal by your opinion.
  1. A simple and quick way to translate the current webpage, or automatically translating the domain without multiple taps is required for mobile devices.
  2. The popup menu should include an option to choose whether you want to auto-translate the current domain along with the webpage translation functionality.
  3. TWP allows you to display an elliptical popup at the top or bottom (position changeable) by touching three fingers simultaneously, just like in the Chrome browser for mobile. Pressing the button on the far right instantly translates the current page, and pressing the gear button gives options such as 'Always translate this language', 'Don't translate this language', 'Always translate this domain' and 'Don't translate this domain'.

image

@vitonsky vitonsky added features Only for important features for implement and removed questions Further information is requested labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request features Only for important features for implement
Projects
None yet
Development

No branches or pull requests

2 participants