More natural navigation through the puzzle?

[roma0615]

Right now, after the user is done typing a guess, the focus doesn't jump to the next open square. It seems like this behavior would help with getting around the puzzle quickly, so I was wondering if there could be an option to enable this kind of navigation? (Maybe something like autoJumpToNextClue)

If my description wasn't clear, this demo has the behavior I'm describing.
(Also, the above demo's arrowkey navigation works a bit differently as well—it lets you go "through" black squares instead of having to go around them. That might also be desirable for navigability)

[johnpc]

Agreed, this is annoying. Is there at least a workaround? I can't see any callback that I can use to force the focus to the next cell, unless I'm missing something.

[redleeder]

+1 This would be a super useful QoL update for users

[briansmiley]

I have made a fork which implements this! (PR here though it looks like there are a lot of open ones)

CrosswordProvider takes a autoJumpFromClueEnd prop. When true, entering a character at the end of a clue will either progress to the next appropriate empty cell, or jump back to the first empty cell in the current clue

I also added support for tab to navigate between clues