Sorry if the subject is indescriptive. Couldn't think of a better once line explanation. Tried to search and crawl through the previous reports but didn't find anything similar, sorry if this has already been reported.
This isn't a huge issue, but I thought I'd report it anyway. When searching using the global search dialog, trying to input a multi-keystroke character (like ü, é, ŝ etc.) using the umlaut or accent keys, if the search string thus far matches something in the search history, the first history entry gets inserted into the input field, and the final accented character is placed at the end.
Example/how to reproduce (and how I found it).
1. Search for "pokemon galactic battles" (for example)
2. repeat the search with the "correct" spelling:
2.1 type in "pok"
2.2 press the "´"-key (on my nordic layout the key left of backspace)
2.3 This is where the magic happens, the input now reads "pokemon galactic battles"), press "e" to make an "é"
3. Now the search field contains "pokemon galactic battlesé".
This only happens if the accented character isn't the first letter of a word ("my uber 1337 search" vs "my über 1337 search" works fine, but "my non-uber example" vs. "my non-über example" doesn't).
While this clearly isn't correct or intended behaviour, it's also a very minor annoyance, and one that certainly won't be encountered often, so no high priority here. As said, I mostly decided to report this bug just as an FYI, and don't think a lot of effort should be put into fixing it, unless it's an easy fix. I hardly think this could result in more serious bug scenarios or that it's something that would distrupt any regular users use of altbinz.
An easy way to bypass this error is to press delete just before the accent key.
