20-0
THE FOOTBALL ROSTER-BUILDING CHALLENGETHE DRAFT ROOM PLAYBOOK
⛶  MORE ROOM FOR THE BOARD

20-0 Game Fullscreen

Expand opens the larger in-page view directly. Fullscreen asks the browser for native fullscreen and uses the expanded fallback when that request is unavailable.

⛶ 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.

Enter through the player’s own control

On the homepage, find Expand and Fullscreen beside Restart. Choose Expand for the in-page display path without first making a native request. You can enlarge the cover before launch; press Play separately when you want to load the live game.

Use a deliberate click or tap. Browsers can require a direct user action for native fullscreen, and a permission or embedding condition can prevent a request from succeeding.

Restart returns the player to its launch cover. A game-saved draft can reappear when you open it again, so this wrapper action should not be read as deleting progress or creating a fresh roster. Use the current exit control when your only goal is leaving the larger display.

Display controls and session controls have different jobs.Choose Fullscreen for room and Restart only when you intend to close the current player.

Read what happened after the request

Native fullscreen, expanded view and loading states separated
Observed stateWhat it meansUseful 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.

The homepage player will attempt the available display path when you use its control.

The expanded fallback keeps its own exit route

The site’s expanded view gives the player a larger bounded area and suppresses the surrounding page scroll while it is open. The control changes its label so you can leave that view deliberately.

That is useful when native fullscreen is not available for the current device or embedding situation. It is still an in-page presentation: browser controls can remain around it.

The illustration documents the local player wrapper. It is not a promise that every phone will hide its address bar or use the same system fullscreen interface.

Keep the exit control within reach.The fallback enlarges the player without claiming a native browser state.

Leave the display without restarting the draft

  1. Check the current label. Native fullscreen and expanded view expose different exit states.
  2. 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.
  3. Inspect the restored board. Confirm the selected card and remaining vacancy before making another pick.
  4. 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.

Keep the reference handy, then make the next choice on the actual draft board.

Play 20-0
Inside the draft