You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried your solutions today, but I reminded that I tried them when I implemented this search box and both solutions didn't work as expected. I tried again today, and I confirmed they didn't work.
This solution also cause a scrolling issue when you add a long text. Tags and the query text are separatedly scroll.
(Sorry, these explanations are probably hard to understand. I will add more details if I have time and motivation... 🙏)
Currently, I'm rewriting the search input with contenteditable, but the progress is not good.
I heard an opinion that contenteditable is too complex just for adding rich components like tags, so I'm wondering if I should consider different approach without contenteditable.
I also considered to use a text input component library to allow adding something like the tags, but I have not found such library yet.
Let me know if you find such a library. Unmaintained or non-Vue components may help me too.
The problem
Characters are slightly chipped when inputting a small number of double-byte characters.
Release version
Latest
Operating system
Chome
Edge(Chomium)
Firefox
Safari
Chome
Safari
Safari
Chome
Samsung Beower(Chromium)
Steps to reproduce the behavior
Enter a double-byte character (e.g., "あ") in the search input box.
Log files
No response
Screenshots
Window Edge, Firefox and Android Chrome(Remote debuggiing)
Additional context
↓It is calculated in the updateSearchBoxWidth function, but it is slightly narrower
https://github.com/xicri/genshin-dictionary/blob/main/components/elastic-searchbox.vue#L40-L46
A slight increase to 1.05 is fine.
However, I feel that it is okay to just remove the updateSearchBoxWidth function and set width: 100% in css
https://github.com/xicri/genshin-dictionary/blob/main/components/word-list-search.vue#L216-L218
↓
The text was updated successfully, but these errors were encountered: