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
If a game runs with rule GoDisputeResolutionRuleNonAlternatingPlay and the game is resumed to settle a life & death dispute, the app shows an alert that lets the user choose which color should play next. Currently the alert shows the alternating color on the right button, and the non-alternating color on the left button. The result is that the same alert sometimes shows colors in the order White/Black and sometimes in the order Black/White. This could be confusing for a user who repeatedly encounters the alert and expects the colors to be in a stable position.
The alert should be changed so that it always shows the color in the same position. The order Black/White seems appropriate because I generally think of the colors in this order (probably because black plays the first move of the game) and because my reading order is from left-to-right.
The text was updated successfully, but these errors were encountered:
If a game runs with rule
GoDisputeResolutionRuleNonAlternatingPlay
and the game is resumed to settle a life & death dispute, the app shows an alert that lets the user choose which color should play next. Currently the alert shows the alternating color on the right button, and the non-alternating color on the left button. The result is that the same alert sometimes shows colors in the order White/Black and sometimes in the order Black/White. This could be confusing for a user who repeatedly encounters the alert and expects the colors to be in a stable position.The alert should be changed so that it always shows the color in the same position. The order Black/White seems appropriate because I generally think of the colors in this order (probably because black plays the first move of the game) and because my reading order is from left-to-right.
The text was updated successfully, but these errors were encountered: