Why a browser game makes you click before it starts: the rules browsers set for games

Click to play, silent music, a controller that seems dead: most of the small pauses at the start of a browser game are rules browsers set so a page has to wait for you before it makes noise or sees your hardware.

Beau Kennedy

A glowing frame in the dark with a pulse of light at its centre and still sound waves around it

You load a browser game, and instead of the game you get a big button that says click to play. Hit it, and the music still might not start. Plug in a controller and nothing happens until you mash a face button. It feels like the game is fumbling the kick-off. It isn't. Most of those pauses come from rules the browser sets, and each one exists so a web page can't do something to you that you didn't ask for.

The quick version: a web page is allowed to show you things, but it has to earn the right to make noise or see your controller, and a click, a tap or a button press is usually what earns it. Once you know which rule sits behind which pause, the rituals stop looking like bugs and start looking like a fair deal.

Sound waits for you to do something first

This is the one that trips people up most. Browsers hold back media that tries to play on its own. In April 2019 Mozilla wrote on its blog that on sites that autoplay video or audio, Firefox would "stop the autoplay before it can start". To hear it, you click play, or you add a site you trust to your permissions list so it plays from the get-go.

The reason is obvious the moment you picture the web without it: every tab you open blaring at you before you've read a word. The cost lands on games, which want their music and effects from the first frame.

Look at how itch.io, the indie storefront, handles it. Its HTML5 documentation for creators says games need a click to start by default, which keeps the game from slowing your browser down while the page loads, and it warns developers who switch auto-start on that "audio may be muted on some browsers". So the click-to-play screen isn't wasted time. It's the game waiting for you before it does anything noisy or heavy.

If a game still comes up silent after you've clicked in, check the obvious things first: the tab isn't muted, and the site isn't on the blocked side of your browser's autoplay settings.

Your controller stays hidden until you press something

Controllers get the same treatment for a different reason. MDN's guide to the Gamepad API, the standard browsers use to read controllers, explains that when a pad is already plugged in as the page loads, the page isn't told about it until "the user presses a button or moves an axis". In Firefox, MDN adds, gamepads are only exposed to a page once you interact with one while the page is visible, and the point is to stop controllers being used for fingerprinting: identifying you by the hardware you have plugged in. Once you've used one pad, any others you've connected become visible too.

That's the system working as designed, and the fix is simple. If a browser game says "press any button" and your controller seems dead, it probably isn't. Press a face button or nudge a stick with the game's tab in front, and the game should see it.

There's a developer side to this as well. MDN tells developers to read the list of connected pads every frame rather than trusting a reading from an earlier event. Our read: a game that follows that advice is the one most likely to keep up when pads come and go mid-session.

Fullscreen is the game's button, not the page's

Fullscreen follows the same ask-first logic. Under the web's Fullscreen standard, a page can only take over your screen in response to something you did, like a click or a key press, so a site can't suddenly fill your display and pass itself off as your browser or your desktop. A game can't just launch fullscreen; it needs you to hit a button.

The site hosting the game gets a say too. itch.io's documentation says it can generate a fullscreen button for a game whose engine doesn't provide one, overlaid on the bottom right of the page when the game is embedded. On phones, games marked as mobile friendly launch straight into fullscreen. Games without that flag still run, but itch.io shows a warning that the game may not work on mobile.

So if you want a browser game to fill the screen, look for that button rather than fighting the browser. And if a game hasn't been flagged for mobile, take the warning seriously: it's the developer telling you they haven't promised it will play on a phone.

Where it gets messy

None of this is identical everywhere. Browsers handle autoplay differently and settings vary, which is why itch.io's warning says audio may be muted on "some" browsers rather than all of them. A game that's built around the rules can wake up its sound and its controls in one start screen. One that tries to skip the click is the one most likely to come up silent, and that's on the game, not your speakers.

So treat the first click as part of the game. Click into the window before you judge the sound. Press a button before you assume the controller is broken. Use the game's own fullscreen button. The browser isn't getting in your way: it's making the page ask first, and that's a trade worth taking.

Sources

More from Xarmo News