By default, when you search on the search page, it does not search for kanji-only definitions. The URL will look something like this: `chrome-extension://.../search.html?query=幷` or `chrome-extension://.../search.html?query=幷&type=terms&wildcards=off` which has no results....

I suspect this has something to do with UTF-16 surrogate pairs. That is, the kanji you posted are technically represented as two "characters" which are rendered as a single glyph,...

That's a browser difference that is unrelated to Yomichan. 飛とび移うつる

The best you'll able to do with Yomichan is to add this custom CSS rule: ```css rt { user-select: none; } ``` but that will only affect text inside Yomichan's...

The issue described in #1152 should be fixed in the latest release. If you describe the issue you're seeing, I can take a look at that also; the additional CSS...

Change _Result grouping mode_ to _Group related terms_, then adjust _Primary dictionary_ and _Secondary dictionaries..._ (which appears below it).

Assuming you still have this issue, can you enable the _Show debug information_ option on the settings page and then log the error information to the debug console, then screenshot...

This issue is because Chromium's [document.caretRangeFromPoint](https://developer.mozilla.org/en-US/docs/Web/API/Document/caretRangeFromPoint) function doesn't return text from inside a shadow DOM, even if it's an open shadow DOM. Contrasted with Firefox's [document.caretPositionFromPoint](https://developer.mozilla.org/en-US/docs/Web/API/Document/caretPositionFromPoint), which does return the...

@pkch This is late since I probably briefly looked at this thread a while back but then forgot about it. I just now got around to implementing a new fix...

Do you have the _Enable Google Docs compatibility mode_ option enabled on the settings page?