Mozilla filed a standards-positions opposition to Chrome’s Prompt API after Blink published an intent-to-prototype for in-browser LLM access.
Key Takeaways
The Prompt API proposal comes from @domenic and is tracked under the webmachinelearning/prompt-api explainer on GitHub.
Blink’s intent-to-prototype triggered Mozilla’s formal opposition via the mozilla/standards-positions issue tracker.
Mozilla’s concern centers on interoperability: other browsers would have to license Google’s model or ship a quirks-compatible alternative.
No WebKit standards position was recorded at the time of Mozilla’s filing.
Hacker News Comment Review
Commenters broadly agree Mozilla’s opposition is warranted: Chrome’s ~dominant market share means a Google-model-tied API could function as platform lock-in, not a true standard.
A recurring technical objection is that no cross-browser implementation exists beyond Chrome (and Edge with Phi-4 mini), so there is nothing ready to standardize yet.
One counterproposal gaining traction: define “standard models” with public-domain weights that behave identically across browsers, similar to how web-safe fonts work.
Notable Comments
@varun_ch: proposes browser vendors agree on standardized, unbranded model weights released to the public domain, interchangeable across browsers like CSS colors.
@fg137: notes only Chrome and Edge (Phi-4 mini) support any form of this API, making standardization premature and the proposal a potential abuse of market position.
