Error highlighting after typing the answer

Anki version: ⁨2.1.55 MacOS

I am using typing in my cards and after the latest release I noticed that the error highlighting doesn’t work as expected.
If I miss a letter in the word. Here “conveable” instead of “convenable”:

The result of validation is a bit confusing for me:

I see twice the correct result with grey highlight on the missing letter. Instead, I would expect to have my invalid input “conveable” to be compared with “convenable” so I would better know what is wrong.

Can confirm, I’ve had the same issue since 2.1.55.

If I recall correctly, the rationale here is that including the missing letter in the input makes it clearer that it was wrong - if it’s excluded, it looks as if the entire input text is correct because it’s all green.


@dae if so, it is not that consistent. For example, if I put nothing into the input field, then during the validation on the top is an empty space presented and on the bottom - the correct answer. Then, why if I miss only a letter, I cannot see the input I made? At least some red highlighting would be welcome :thinking:

Zrzut ekranu 2022-12-30 o 11.55.25

“no input” is treated as a special case, for when users want to go through cards without typing (eg when they’re on mobile and don’t want to deal with touchscreen input).

Red is now reserved for when you entered something incorrectly, instead of omitted something:


I’ve had some different issues with the error highlighting too. I think these have all started recently, I never noticed issues before.

For example:
I typed in 스다뜸다 and the correct answer was 다.
It counts the second character 다 as wrong even though that one was correct.
I can reproduce this with an English example, for example if the correct word is “door” and I type in “eoer”, it would count the o as wrong. I’m not sure if this is intended.

Other things seem to go wrong whenever a character is repeated in the correct word.
For example the correct word is 민주주의.
If I type in 민주의 or 민의, I would get this:
Even though I did type in the last character 의, it looks like I didn’t.

I can even get it to give a “correct” answer that’s actually wrong, for example when I switch characters around and type in 민주의주, I get this:
The second 주 has disappeared in the correct answer.

These ones I’m not able to reproduce with an English word. For example if I type in “dor” or “doro” for “door”, the highlighting works correctly. So it might be an issue only for specific languages.

Anyway, it’s not a big deal or anything, but there’s definitely something wacky going on.

I’ve logged this on Investigate switch to difflib · Issue #2305 · ankitects/anki · GitHub

1 Like

Thank you @dae
Not sure if this helps, but I have also noticed that in iOS version of the app the comparison in the same case works different. If I put “un case” instead of “une case”:

Then the validation result looks reasonable and I can better understand what I did wrong:

The next AnkiMobile update will match the behaviour of the desktop. I think my thinking at the time was that it’s more useful to be able to see the actual character you missed in the input string (eg “e” in grey) rather than just a “-”, as then you have to cross reference with the bottom section. I don’t have strong feelings about it, and perhaps we can do a forum poll in the future to see which people prefer.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.