Open tats-u opened 1 year ago
https://developer.mozilla.org/docs/Web/API/Event/composed must be used to fix this problem.
This may be due to https://github.com/algolia/autocomplete
I cannot reproduce this in macOS Firefox, but Chinese input methods work differently and I don't know how to use the Hiragana input method... In any case, Docusaurus does not provide the search modal, so we will track https://github.com/algolia/autocomplete/issues/1135 instead.
@Josh-Ce I don't have a mac, but can't it be reproduced in Microsoft Pinyin in Windows parallels either? (I'll try it later in physical Windows though)
Unfortunately I don't have access to a Windows machine either :/
fyi how to enable Japanese IME in macOS
Yeah I do have the Hiragana keyboard, I just never know how to use it.
Seems to work well. It may be Windows specific.
I was able to test in Google Pinyin in Windows Sandbox.
Input a sentence→Press backspace until all characters are deleted While I pressed backspace, I found the search bar behaves suspiciously (as if I pressed a space).
woxihuan→[backspace]→・・・→woxih (OK until here)→[backspace]→我系 (IME closed; I can't modify pinyin anymore)
Another example (I just pressed backspace once after typing huanghe)
Google Pinyin: 下载谷歌拼音输入法 Download Google Pinyin Chinese Mandarin Pinyin Input (Direct link: Download Google Pinyin [ 标准版 ] For Microsoft Windows | GeckoandFly Server)
Can macOS + Firefox input Pinyin on the field in this pen successfully?
@tats-u sorry I was quite busy for the last few weeks. Yes, the pen works for me on Mac Firefox, both using Chinese and Hiragana keyboards.
The IME closing seems unexpected, but I can't reproduce it here. Maybe it's a platform-specific issue?
macOS doesn't seem to be affected. Thank you for your cooperation.
FYI in Windows:
https://github.com/algolia/autocomplete/issues/1135#issuecomment-1916879932
We will be able to fix this issue by ignoreCompositionEvents
in the latest autocomplete for CJK languages.
@Josh-Cena Now that the ball is in our court, could you reopen this issue?
@tats-u Could you try it in your environment? Thanks!
Has it been committed in main? It does not look like.
Ah, no, I meant if you wanted to make the code change and test it locally.
I see.
I found that we still have to wait for fix of https://github.com/algolia/docsearch/issues/1043 & https://github.com/algolia/docsearch/issues/1304.
That attribute has not been imported into <DocSearchModal/>
(@docsearch/react
) yet.
We have only to add a line in packages\docusaurus-theme-search-algolia\src\theme\SearchBar\index.tsx
.
Should we use useDocusaurusContext().i18n.currentLocale
to check if that attribute should be designated?
Is there a downside to this being unconditionally applied?
You may want to see:
https://github.com/algolia/instantsearch/issues/5986 https://github.com/algolia/instantsearch/pull/6009
It is up to your team to apply this to all locales. I am against their background, though. The detailed condition (the name of Ithe keyboard app & the language of the keyboard) is not written. I think Gboard (English & Japanese) for Pixel works well.
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
docusaurus-theme-search-algolia
has a bug to prevent from inputting Japanese in Windows Firefox. Other languages, e.g. Chinese, may be affected, too. Chromium-based browsers work well.Reproducible demo
https://docusaurus.io/
Steps to reproduce
Expected behavior
https://user-images.githubusercontent.com/12870451/235352380-d6be7c95-c69b-489d-b8eb-d00d5ecdc499.mp4
(Edge)
Chrome also works well.
Note: this movie uses AV1. Safari may not be supported. Edge requires an this Windows video extension.
Actual behavior
https://user-images.githubusercontent.com/12870451/235352442-ccfbda41-a997-463d-8d56-26a10a3fd361.mp4
Input corrupted at every moment😡
Your environment
Self-service