-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-english characters on default search #108
Comments
I'm having trouble replicating the issue (and our usage in DocumentCloud does appropriately set up a text facet when you paste in Γιάννης or type in other unicode), do you happen to have a page I could hit to see what's happening? |
You can try it here: Just clear out all fields and type in or paste the non-english text. For example, if I type 'a' the 'access' facet is displayed. As soon as I press 'v' (av), the dropdown disappears as there is not match for 'av'. But it seems that it fails with other Unicode chars. So it the url above, if I paste (or type) "John", the dropdown is cleared. If I paste (or type) "Γιάννης", the dropdown stays open with "access" preselected. Tested on latest Chrome and Firefox. |
When typing a text with non-english characters on an empty visual search input, without a facet selected, the default text: ... facet does not get filled in and the text typed is lost.
Works fine for english words though.
For example:
| John | -> Enter -> | Text: John |
| Γιάννης | -> Enter -> | access: | (returns the first facet)
The text was updated successfully, but these errors were encountered: