Persistence has two meanings

A control can remain visible across orientations, or its selected value can remain stored while the control disappears into a menu. Those are different forms of persistence. Do not infer one from the other merely because the interface looks familiar.

A third possibility is a page restoration occurring around the same time as rotation. That can reintroduce a previous view or a session message. Check what the current screen actually says rather than attributing every change to orientation alone.

Begin from a stable state

Rotate only after a round is settled and your fingers are clear of the screen. A grip adjustment can accidentally touch a newly positioned button. Put the phone on a stable surface if that makes the change easier to observe.

After rotation, pause before interacting. Allow the layout to complete its adjustment and identify any control that has moved. The previous location of the information button is not a safe guide to the new layout.

Verify the control set

Use a short inventory rather than checking only that the artwork still appears. Each essential function should be identifiable in its current position.

  • Read the current stake amount and its unit.
  • Locate the information or paytable control.
  • Find sound and other comfort settings if needed.
  • Identify the main action control without pressing it.
  • Check for any notice or unresolved-round status.

There is no need to activate each control to prove it survived rotation. Visibility and clear labelling are the initial checks.

Collapsed menus need careful reading

A compact icon can hide several settings behind one panel. Open it only when its purpose is clear, then read the labels before making changes. A familiar gear or arrow shape is a clue, not a guarantee of what lies behind it.

If a menu covers the stake display, close it and verify the amount again. Where the label remains clipped or ambiguous, stop. A remembered setting is not an adequate substitute for a readable active value.

Resolve unexpected changes separately

If a setting appears different, do not start a round to test it. Inspect the information available and, if necessary, record the layout issue for support. Include orientation and browser details without exposing private account information.

Rotation does not change a recorded outcome, nor does it create a new game state simply by changing the view. If an animation is interrupted, consult recorded round history rather than interpreting missing visual steps as a missing payment. The objective is a clear interface, not a particular result.