we were wondering if you could adjust the text input component. We use it for cloze exercises, and while it works well in general, we often have multiple blanks in a single sentence where a word needs to be entered. However, since the text input only allows one blank per line, this results in an unnecessary number of lines, which also disrupts the reading flow. I’ve attached an example – it’s in German, but it illustrates the problem quite well. I can’t imagine that I’m the only one facing this issue – maybe you already have it on your roadmap?
Apart from Helen, I don’t think anyone else has raised this. Will definitely add it as something to consider; my immediate concern would be getting the screenreader accessibility right.
That surprises me a bit, since cloze exercises are a common tool for assessing knowledge, for example. In educational institutions like ours, they are standard practice.
When it comes to accessibility, you are the experts. If it’s purely about responsiveness, it might already be quite challenging on smartphones to display enough content – having multiple blanks in a single line probably won’t be possible in that case.
I would like to revisit the topic of fill-in-the-blank texts via text input and insist that allowing multiple blanks within a single line would be a useful feature. I understand that you need to consider the demand for certain features. However, if you take a look around, it quickly becomes clear that having multiple blanks on one line is a common standard. It just looks awkward when I have a sentence like this, and it is split into two lines:
The [sky] is
[blue] during the day,
but at night the [sky] is
almost [black].
I can imagine that it’s difficult to set the line break at the right place. However, manually adjusting it doesn’t look any better, especially when the blanks are in separate lines, as seen above.
Honestly, it’s not clear to me why there seems to be so little demand for this.
By the way, the matching component has a similar issue.
I’d still like it to be possible so I’ll push for a feature request on this one 