themoeway / yomitan

Pop-up dictionary browser extension. Successor to Yomichan.
https://yomitan.wiki
GNU General Public License v3.0
1.19k stars 94 forks source link

Yomichan and Kiwi Browser Issue: Text Selection and Copying Problem #210

Closed huannv100 closed 2 months ago

huannv100 commented 1 year ago

I'm using Yomichan on the Kiwi browser with the Scan modifier key set to 'No key.' However, there appears to be an issue with the interaction between Yomichan and the browser, which is preventing me from selecting and copying text as I would normally do without using Yomichan. Is there a solution to this problem?

fauu commented 1 year ago

I'm not entirely sure but I believe the only way you can have working selection currently is to disable "Select matched text" in Scanning options. But the price you pay is losing the highlighting of the matched word. I'm still on a pre-fork version though, so it's possible that the information doesn't apply to this fork.

Edit: The settings shown in https://github.com/themoeway/yomitan/issues/210#issuecomment-1696092041 in my case allow browser text selection without having to disable "Select matched text" in Yomichan.

huannv100 commented 1 year ago

Actually, I'm also using the pre-fork version. I tried disabling "Select matched text," but it still doesn't work. I cannot copy the selected words; it only works about 1 out of 20-30 tries, regardless of whether "Select matched text" is disabled or not.

fauu commented 1 year ago

I found something you could try: in "Scanning" go to "Configure advanced scanning inputs" and make sure "Mouse" is not selected and "Touch" is selected (and below that also "Scan on touch press").

HuanNV9 commented 1 year ago

Thank you. I just tried, but it still doesn't work. Does it work on your end?

fauu commented 1 year ago

Yes, I get the Yomichan popup when I tap on a text and I get a normal text selection when I tap and hold on the text, with working copying and so on. I'm on Yomichan 22.10.23.0, Kiwi Browser 116.0.5845.72, Android 12.

Some other Yomichan settings that could be relevant: in "Configure advanced scanning inputs" I have just a single input defined. "Required inputs" and "Excluded inputs" are both empty, only the "Touch" input type is selected, and below that "Scan on touch press", "...move", "Prevent touch scrolling" are on. At the end of the "Scanning" section under "Support inputs for devices with touch screens", I have "Touch inputs" selected and "Pointer inputs" not selected.

TheMadHau5 commented 1 year ago

I am on the same versions of Yomichan, Kiwi, and Android. I have changed my settings to match what you said, but the selection popup doesn't appear, only the Yomichan popup does. Any ideas?

fauu commented 1 year ago

I'm out of ideas for now. You could try the 10ten Japanese Reader extension instead of Yomichan and see if it works there. It has an option to look up words not by tapping them but by dragging a puck over them, which should interfere less with the normal text selection mechanism.

huannv100 commented 1 year ago

Thank you. Unfortunately, I couldn't get it to work. Actually, I'm using Yomichan for Korean.

Mansive commented 1 year ago

Using these scanning options allows you to select text better at the cost of reintroducing accidental popups when swiping across pages. An alternative is to hold tap on special characters such as quotes or periods, then drag to select the actual text you want. image

djahandarie commented 10 months ago

@huannv100 Are you having the issue on the latest release of Yomitan? Did the above settings help you?

huannv100 commented 10 months ago

The settings didn't help. I haven't tried Yomitan because I believe it doesn't currently support Korean.

asodugf12 commented 10 months ago

I found a workaround to this issue. If you hold on letters that cannot be parsed by the dictionary, for example in japanese the small ya (ゃ), yo (ょ), yu (ゅ) and the small tsu (っ). Things like ちゃ, きゅ and った are great places for this.

Edit: Punctuation marks like 。, 、, !, ?are easier and more reliable too!

Kuuuube commented 2 months ago

This should be fixed with the addition of touch tap touch option.