GTA 3 Browser Keyboard Controls: Mouse, Driving and Fullscreen Tips

Browser game controls have one extra layer compared with a desktop executable: the browser itself also wants keyboard shortcuts, mouse focus and Escape behavior. GTA III Browser therefore coordinates web input with the re3 engine so gameplay receives keys without trapping the user permanently inside the canvas.

Core movement and driving controls

Exact mapping can vary with the re3 configuration and build. The browser layer's job is to deliver input cleanly; the engine still decides the final in-game action.

Why you may need to click the game first

Browsers protect mouse capture and some input behaviors behind user interaction. Clicking inside the game canvas lets the page request pointer lock so mouse movement can be treated as relative game input instead of a cursor moving to the edge of the screen.

Pressing Escape normally releases pointer lock. This is intentional: a browser game should always give the user a predictable way to regain control of the page.

Fullscreen controls

The homepage has a Fullscreen control, and the dedicated game window also provides fullscreen access. Native browser fullscreen may be exited with Escape. Even when native fullscreen is denied, the site uses a page-sized game window so the loader and canvas remain isolated from the article content underneath.

If the canvas size looks wrong after entering or leaving fullscreen, give the browser a moment to resize the backing buffer. The launcher listens for fullscreen changes and recalculates the display size.

Keyboard and mouse remain the most complete input method for the current browser build.

Avoid browser shortcuts during play

Some key combinations belong to the browser or operating system rather than the game. The launcher prevents selected defaults in the game context, but system-level shortcuts can still win. Avoid using browser navigation keys or OS shortcuts as game bindings.

If a key appears stuck after switching tabs, click back into the game. The input layer includes focus-loss recovery because a browser can stop delivering key-up events when focus disappears at the wrong moment.

Touch Controls AUTO / ON / OFF

The current homepage includes a touch-control preference that cycles through AUTO, ON and OFF. At this stage it stores the player's preference and emits a browser event for future on-screen control work. It should not be interpreted as a finished touch HUD yet.

For reliable play today, use a physical keyboard and mouse. Future touch controls can read the saved preference without redesigning the homepage settings panel.

Gamepads and browser support

Modern browsers expose gamepads through standard APIs, but complete gamepad behavior depends on the engine input path and controller mapping. If a controller is not recognized, test keyboard input first to separate a gamepad mapping issue from a broader engine problem.

USB and Bluetooth controllers can also differ in browser-reported layout. A controller working in another website does not automatically guarantee the same button mapping in re3.

Input troubleshooting checklist

• Click the canvas after the game menu appears.
• Press Escape once if the pointer seems trapped or mouse movement is wrong.
• Return focus to the game after Alt-Tab or switching tabs.
• Disable extensions that intercept keyboard shortcuts if a specific key never reaches the page.
• Test a standard US-style keyboard layout if unusual layout mappings create confusion.
• Hard-refresh after a site update if old input JavaScript is still cached.

If the entire game is frozen rather than just input, use the browser startup troubleshooting guide instead.