Mozilla engineers have fired a warning shot across the bow of Chrome’s latest AI push. In a stark update to their standards-positions repository, the Firefox maker reaffirmed its opposition to the Prompt API. “We continue to oppose this API, and feel it has severe negative consequences to the interoperability, updatability, and neutrality of the web platform,” Mozilla Standards Positions Issue #1213 states bluntly.
The fight centers on a proposed web API that would let sites send text prompts to on-device large language models—think Gemini Nano in Chrome—for generating responses like summaries or translations. Google, via its Web Machine Learning group, wants this baked into browsers. Chrome’s intent-to-ship notice on Blink-dev signals plans to roll it out soon. But Mozilla sees traps everywhere.
Short version? The API ties the open web to proprietary models. Developers would craft prompts tuned to specific LLMs’ quirks. Swap models? Everything breaks. “This will result in Mozilla and Apple having to licence Google’s model, or ship a model that’s quirks-compatible with the Google model in order to be interoperable,” the issue warns. Neutrality shattered. Browsers locked into one vendor’s AI stack.
Brian Grinstead, a Mozilla graphics lead, laid out the case early. Labeled the position “negative” back in June 2025. No backing down since. Recent pings—from tidoust on April 9 and others this week—keep it alive as the spec inches toward W3C browser-specs inclusion.
And the developer buy-in? Thin. Proponents cite a smattering of feedback: a GitHub thread here, an X post there. Mozilla calls for real-world testing via web extensions first. They’ve prototyped just that—local inference in extensions, letting devs pick models without browser gatekeeping. Users know it’s experimental. No standards rush.
Google’s own rules add fuel. Their Generative AI Prohibited Uses Policy bans certain prompts, forcing devs to query model IDs and comply—or risk bans. “Developers may query models for their ID to comply with varying terms and conditions,” Mozilla notes. Fragment the web further? No thanks.
This isn’t just technical nitpicking. It’s a standoff over the web’s soul.
Recent buzz on Hacker News amplifies the stakes. “Mozilla’s Opposition to Chrome’s Prompt API,” a top thread from April 30, draws 64 points and 17 comments. Posters flag fingerprinting risks—unique model behaviors as tracking vectors. Hard to spoof. Privacy hit.
X lights up too. Jamie Birch notes Gecko maintainers’ concerns need spec fixes before implementation. Original daisuke quotes the opposition directly. Cosmicjs bundles it in their rundown with nuclear policy flips and OpenAI gaffes. Even IlSoftware.it covers it in Italian: “Mozilla contro la Prompt API di Chrome.”
WebKit? Silent so far. Their standards-positions repo has a related ML Prompt API issue (#495), but no fresh word. Apple, wary of AI web creep, might align with Mozilla. Or not. History shows rifts—think WebKit’s iOS lockdown delaying Firefox entry by years, as Mozilla griped in antitrust filings.
Interop suffers most. Origin trials? Mozilla scoffs. Extensions beat them for cross-browser testing. No model lock-in. Signal to users: this is beta.
But Google presses. Chrome’s explainer touts local SLMs for privacy. Labs.thinktecture demoed Gemini Nano prompts. Tyingshoelaces blogged it—now archived. A Google survey slides positive quotes. Still, Mozilla demands more: broad dev support, model portability proofs.
Fragmentation looms. Chrome ships solo? Sites detect it via user-agent or heuristics. Others scramble—or ignore. Web shrinks.
Mozilla’s playbook works. They’ve nixed Web Environment Integrity, pushed back on others. Here, they offer paths: extension APIs, userland experiments. Let ideas prove themselves.
The clock ticks. W3C looms. Blink-dev hums. Will Chrome pause? Or forge ahead, betting devs follow? Firefox users—3-5% global—might not notice. But the web? It feels every fracture.
One thing clear. Mozilla won’t budge. Neutral web. Interoperable. Updatable. Pick your side.


WebProNews is an iEntry Publication