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
Feedback from a user of saan (but I believe this problem is a general one): When having clicked on a Skolt Saami word, say ǩiõččâd, and wanting to continue searching in the fin-sms dictionary, the user used the menu to the left of the search bar, but clicking on a different language pair did not actually change what dictionary was used.
The user had experienced this in Edge on Windows and Safari on a phone, and I have confirmed the behavior in both Firefox and Chromium on Linux.
The text was updated successfully, but these errors were encountered:
The dictionary selector dropdown right now does nothing, and I can't find the code for what it is supposed to do. I can find some code for handling the dropdown itself, but I can't see that it performs any kind of client-side work that would affect how the search bar on the same page behaves.
The search bar itself on the detailed results page works, but it takes you back to the "standard" search results page, you don't stay on the "detailed" search page, as one may or may not have expected. That's maybe a bit confusing.
Moreover, the dictionary selector dropdown contains the same functionality as the dictionary selector on the front page, presumably built as a simple dropdown just for the search bar on the details results page, which is also not ideal. How to switch dictionaries should be the same everywhere.
Feedback from a user of saan (but I believe this problem is a general one): When having clicked on a Skolt Saami word, say ǩiõččâd, and wanting to continue searching in the fin-sms dictionary, the user used the menu to the left of the search bar, but clicking on a different language pair did not actually change what dictionary was used.
The user had experienced this in Edge on Windows and Safari on a phone, and I have confirmed the behavior in both Firefox and Chromium on Linux.
The text was updated successfully, but these errors were encountered: