The developer of Google's 2010 Pac-Man anniversary doodle has described how a seemingly small autoplay decision combined with a popular Firefox extension to produce unexplained game sounds on computers around the world. The retrospective offers a case study in how two independently reasonable software behaviors can interact in a way neither team anticipated.
Google created the interactive homepage feature for Pac-Man's 30th anniversary. Designer and developer Marcin Wichary rebuilt the game with HTML and CSS, adapting the maze to resemble Google's logo and adding a two-player Ms. Pac-Man mode behind the Insert Coin control. Sound required Flash support, which was common enough in browsers at the time to make the original game's opening music, movement sounds and death sequence available on the homepage.
The team also decided the doodle should begin playing after 10 seconds without user activity. On the visible Google homepage, that seemed unlikely to cause much trouble because visitors normally typed a search or left quickly. The combination meant, however, that an untouched page could eventually play sound without a click or keypress.
The unexpected trigger was CoolPreviews, then a widely used Firefox extension for previewing links. According to Wichary's account, the extension opened a website invisibly in the background when Firefox started, apparently to warm a cache or because of a leftover default. On the doodle's launch day, that site was google.com. Ten seconds after a user launched the browser, an unseen Pac-Man session began and its siren-like sound emerged from the speakers.
People reporting the problem could not solve it by closing the visible Pac-Man tab because they had never opened one. Some did not know the browser or extension was running. That made the behavior resemble a malfunction or an unwanted program rather than a celebratory game. The doodle team connected the reports to CoolPreviews only after investigating why the normal workaround failed.
Wichary patched the live homepage within hours. The revised behavior added a visible mute control and required a user interaction, such as a click, keystroke, touch or activation of Insert Coin, before audio could begin. Because the background preview did not interact with the game, the change stopped the hidden sound while preserving audio for people who chose to play. Modern browsers commonly impose similar user-activation requirements on audible media.
The account is also a reminder that testing a component in isolation cannot reveal every production interaction. Google's game behaved as designed, and the extension behaved according to its own startup logic, but their composition violated the user's expectations. Sixteen years later, the episode reads less as a curiosity about Flash than as a durable lesson: background loading and automatic media need conservative defaults because software cannot know what other code will place a page in front of—or hide it from—the user.
