Thanks for all the nice comments!
I’m glad that so many of you think that my script might be useful.
I assume you mean transitive/intransitive errors that occur at meaning questions? I have not implemented anything specifically for this case, but if you for example write “to be wet” (intransitive) when asked for the meaning of 湿らせる (transitive), then my script will display items with the meaning that you have entered:
I think in most cases, the other half of the transitive/intransitive pair should be ranked at the top. I could probably try to mark this as a new guess type “intransitive⬄transitive” instead of the default “丸⬄九”, but I don’t know if I can do this accurately enough.
I’m a bit surprised that in your guesses list the vertical scrollbar is not displayed. When I tested my script on Firefox, it added weird line breaks into guesses unless I set the scrollbar to be always visible:
Therefore I tried to make it so that on Firefox the scrollbar is forced to be visible, even if there is nothing to scroll. It seems like it didn’t work, so I hope that you don’t get those ugly line breaks. However, now that I think about it, maybe the superfluous scrollbar is even uglier than the line breaks.
Does anyone with css experience know how I could fix this? Firefox seems to first calculate the necessary width for the div with the css-grid so that everything fits nicely, but afterwards realizes that it needs to draw a vertical scrollbar. It then takes the needed space from the grid away, which results in the grid width shrinking. Some text does not fit anymore and line breaks are added. Google Chrome on the other hand makes the div a bit wider whenever it needs to draw the scrollbar, so no line breaks appear. Or maybe this happens exclusively in the Firefox Developer Edition that I have used for testing.