1012: Who Decides What Ships on the Web?

Summary of 1012: Who Decides What Ships on the Web?

by Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers

1h 9m•June 15, 2026
Listen to Episode

Overview of 1012: Who Decides What Ships on the Web?

Wes Bos and Scott Tolinski interview Jake Archibald, now at Mozilla, about how browsers decide what to ship, how web standards get prioritized, and why Mozilla is cautious about Chrome’s new Prompt API. The conversation covers Firefox’s resource constraints, the Interop process, recent and upcoming standards like heading offset, view transitions, popovers, anchor positioning, Web Serial, and image formats like AVIF and JPEG XL. They also dig into the tension between shipping AI-native browser APIs and preserving an open, neutral web.

Main Topics Discussed

Jake Archibald’s background and move to Mozilla

  • Jake recaps his path from the BBC to Google (a decade in Chrome DevRel), then Shopify, and now Mozilla/Firefox.
  • He says he missed working on web standards and is back in a role focused on developer relations and browser feature prioritization.
  • He mentions notable work across his career:
    • Service workers
    • Fetch
    • View Transitions
    • CSS linear easing

How Firefox decides what to ship

  • Mozilla’s top priority is making sure the web works in Firefox, especially for major sites and services.
  • The first question for any feature is: if Firefox doesn’t ship this, will sites break?
  • After compatibility, Mozilla looks at:
    • developer value
    • impact vs. engineering cost
    • whether a feature meaningfully improves the web

Firefox’s pace and constraints

  • Jake says Firefox often ships features faster than people expect given its smaller team and lack of billionaire backing.
  • He notes that Firefox is usually:
    • first
    • second
    • or at least not far behind
  • He contrasts Firefox’s priorities with browsers that may ship features based on internal needs or business incentives.

AI, the Prompt API, and the open web

What the Prompt API is

  • Chrome’s Prompt API lets websites access a local language model in the browser.
  • It involves:
    • creating a model
    • passing in a system prompt
    • receiving text output
  • Chrome’s implementation downloads a very large model locally, which raised concern because it happens without a permission prompt.

Mozilla’s objections

Jake explains Mozilla’s concerns with the Prompt API on several fronts:

  • Non-determinism problem

    • LLM output varies by model.
    • Web APIs normally need consistent behavior across browsers.
    • Developers would end up “user-agent sniffing” models to tune prompts.

  • Cross-browser compatibility

    • If each browser uses a different model, the same prompt can behave differently.
    • This creates a new version of the old browser-quirk problem, but amplified.

  • Policy and neutrality concerns

    • Chrome’s terms include restrictions beyond law, such as political/misleading-content clauses.
    • That makes the API feel less like an open web standard and more like a Google-controlled platform.

Mozilla’s preferred direction

  • Jake says a limited, capability-specific AI API can make sense.
  • He sees more promise in APIs like:
    • translation
    • text-to-text tools
    • scoped browser features with predictable behavior
  • He is more skeptical of a broad “prompt anything” API on the open web right now.
  • He suggests a better path might involve:
    • user-selected local models
    • browser-developer negotiation over available models
    • or waiting until models become more consistent

Broader AI/web concerns

  • The hosts discuss fear that the browser could become less central if AI lives only inside chat apps.
  • Jake’s view: most real-world AI usage already happens through browsers or web views, but usually against a model the developer can control.
  • He emphasizes that the browser should preserve neutrality and not become a gatekeeper for AI behavior.

Standards and browser features Jake is excited about

Interop and prioritization

  • Jake explains that Mozilla uses Interop ranking data and developer sentiment to help decide what to prioritize.
  • Features that can break or significantly degrade sites get more urgency than nice-to-have enhancements.

Features discussed

  • Heading offset

    • Lets developers offset heading levels inside a container.
    • Useful for components, Markdown, includes, and nested content.
    • Helps solve the long-standing “what heading level should this component use?” problem.
    • Also enables CSS selection based on semantic heading level rather than tag name.

  • Cross-document view transitions

    • Jake is personally enthusiastic about them.
    • They’re valuable because they add polish without breaking sites that don’t support them.

  • Popover and anchor positioning

    • Important building blocks for future UI patterns, including custom select-like components.

  • Text box trim / margin trim / animating display: none

    • Jake says animating display: none is especially interesting because it solves common UI issues.
    • He notes the feature must preserve accessibility and avoid interaction bugs by making elements inert during transitions.

  • HTML and Canvas

    • He’s interested, but Mozilla is cautious.
    • Concerns include performance regressions and giving developers too much low-level power without the years of optimization browser engines usually provide.
    • Still, Mozilla has been helping shape the API design.

Image formats and performance

AVIF vs. JPEG XL

  • They discuss JPEG XL:

    • Jake describes it as an image codec that’s better in some low-compression cases, but not necessarily better overall.
    • Mozilla is testing an implementation written in Rust.
    • JPEG XL’s advantage is that it’s a true image format and supports progressive rendering well.

  • They also discuss AVIF:

    • AVIF is already broadly supported in major browsers.
    • It’s improving, including better quality algorithms influenced by JPEG XL research.
    • Jake notes it’s good to see competition improving image delivery.

Progressive rendering

  • JPEG XL can show progressively refined image quality as bytes arrive.
  • AVIF can also do progressive-style rendering through video-like techniques.
  • Jake explains why video is still the right answer for actual animation rather than animated image formats.

Firefox features, dev tools, and daily-driver advice

Web Serial, Web MIDI, and device access

  • Firefox has now shipped Web Serial.
  • Jake says Web MIDI is likely to follow, with possible support for Web Bluetooth and Web USB later.
  • Mozilla had previously been cautious about these for security reasons, but heard enough from developer users to reconsider.
  • The argument in favor: browser-based device access is often safer than installing sketchy native apps.

DevTools and Firefox Nightly

  • Jake praises Firefox DevTools and encourages people to file issues if they’re missing features.
  • He recommends using Firefox Nightly if you want to test new web features and help by reporting bugs.
  • He says Nightly is unusually stable compared with Chrome Canary or Safari Technology Preview.

Developer Edition

  • He says Firefox Developer Edition is still being reconsidered and doesn’t currently offer much beyond a cool icon.
  • His take: most web developers already have multiple browsers open, so “for developers” branding is not always meaningful.

Takeaways

  • Browser vendors balance three forces:
    • compatibility
    • developer demand
    • internal engineering realities
  • Mozilla is especially focused on:
    • preserving open standards
    • avoiding platform lock-in
    • shipping features that improve the web without fragmenting it
  • The Prompt API is the episode’s biggest controversy:
    • useful in concept
    • problematic as an open-web standard right now
    • especially because of model inconsistency and vendor control
  • A lot of the most useful browser innovation is still in “boring” plumbing:
    • heading semantics
    • animations
    • popovers
    • positioning
    • device access
    • image rendering

Notable Side Notes / Fun Moments

  • Jake recounts getting badly sunburned during an episode shoot and using YouTube makeup tutorials to cover it up with green concealer.
  • He jokes about using matte makeup because after-sun would make him look like a “WebGL demo gone wrong.”
  • The discussion includes several humorous examples of how British and American speakers sound to each other.

Sick Picks / Recommendations

Jake’s picks

  • Japanese sun cream

    • Especially products like Nivea or “UV Aqua Rich.”
    • Praised for being lightweight and effective.

  • TrackMania

    • A racing game he compares to the feel of go-karting.
    • He likes the fast reset loop and the precision challenge.

  • Clues by Sam

    • His most-played daily puzzle game.
    • He recommends it as a strong logic game that rewards careful reasoning.

Shoutouts / Where to find Jake

  • Jake points listeners to the Firefox Web Dev social accounts, where he posts:
    • standards updates
    • feature demos
    • polls and developer feedback requests
  • He’s active across:
    • YouTube
    • TikTok
    • Instagram
    • Bluesky
    • Mastodon
    • X
    • Threads
    • Facebook