Open RekiDunois opened 2 years ago
@RekiDunois
Because Edge is also Chromium based, I only tested it on Chrome. The bug cannot be reproduced on Chrome, I think it is mostly caused by the conflict of the Katakana to English extension. Could you provide the details about the Katakana to English extension you used?
https://github.com/Arnie97/katakana-terminator I use this katakana-to-English userscript. But I don't think this is the reason, because I try it in chrome and firefox, and this bug did not show up.
@RekiDunois several months ago, I fixed a similar bug. Which version of mirigana you are using in Edge. I tested the 1.2.1 version on Edge but cannot reproduce.
1.2.1 too.
cant reproduce
I am using edge, is edge cause this problem?