⛶ Two display paths can give the board more room
The 20-0 game toolbar has both Expand and Fullscreen. Expand deliberately opens the larger in-page view. Fullscreen asks the browser for native fullscreen and uses that same expanded fallback if the request cannot be completed. Both controls change presentation, not the roster.
Native fullscreen
The browser places the player in its fullscreen presentation. Browser and device support determine what controls remain visible.
Expanded view
The site enlarges the player over the surrounding guide. It gives you room inside the page while browser chrome may remain.
The two paths serve the same reading need but are not the same browser state. Expanding the view also does not launch a second draft or change an offered player.
Read what happened after the request
| Observed state | What it means | Useful next action |
|---|---|---|
| The player occupies native fullscreen. | The browser accepted the request. | Use its fullscreen exit control when finished. |
| The player expands over the page. | The site is using the in-page fallback. | Use Exit expanded view or Escape where available. |
| The normal cover is still visible inside a larger area. | The display changed, but the game has not been launched. | Press Play if you want to load the game. |
| The game is blank in either display. | More screen space did not resolve loading. | Use the loading checks rather than repeatedly expanding. |
| A profile or access prompt appears. | The live game is asking for a session condition. | Follow that prompt; display size does not grant access. |
🔎 Check the capability advertised by this browser
This check reads a browser capability signal. It does not enter fullscreen, change a game, or prove that a later embedded request will be accepted.
Leave the display without restarting the draft
- Check the current label. Native fullscreen and expanded view expose different exit states.
- Use the available exit control. On many desktop browsers, Escape exits a fullscreen presentation; device interfaces can also provide their own exit gesture or button.
- Inspect the restored board. Confirm the selected card and remaining vacancy before making another pick.
- Keep Restart separate. Closing the player session is not necessary merely to return to ordinary page reading.
If the browser itself leaves fullscreen because you switch applications or use a system control, inspect the visible state instead of assuming the game restarted. A presentation change and a new draft are separate events.
On iPhone and iPad, trust the visible state
Fullscreen support depends on the browser, operating system, document, and kind of content. A familiar video-style fullscreen experience does not establish that an embedded interactive football game can use the identical path.
Use the available expanded fallback when native fullscreen is not offered. Rotate only when the extra width improves the comparison, and keep a visible way back to the normal layout. Do not repeatedly reload an active run in an attempt to force a system display mode.
A capability signal is also narrower than a success guarantee. The browser can advertise fullscreen while a particular request is still restricted by the current frame or user-action condition.
Use the larger view for a specific reading problem
More room should make a 20-0 game decision easier to inspect: the stat units, the selected player-season, or the legal destination. If all three were already clear, display size alone will not improve the choice.
Return to the main player to use its actual control. Use the mobile reading sequence for cramped cards and the recovery branches if a blank player persists. Those problems need different actions from simply entering and leaving a larger view.