You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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)
The text was updated successfully, but these errors were encountered: