The Presentation API lets a user agent (such as a Web browser) effectively display web content through large presentation devices such as projectors and network-connected televisions. Supported types of multimedia devices include both displays which are wired using HDMI, DVI, or the like, or wireless, using DLNA, Chromecast, AirPlay, or Miracast.
[Question] Why does the spec require a browser to select the presentation device · Issue #526 · w3c/presentation-api
I've been reading the closed issues and I've skimmed through the spec before posting this. I don't really understand why I'm not allowed to get a list of objects containing the pres...
Present web pages to secondary attached displays | Blog | Chrome for Developers
Chrome 66 allows web pages to use a secondary attached display through the Presentation API and to control its contents through the Presentation Receiver API.
Browser AI API for Utilizing On-Device Models · Issue #178 · WICG/proposals
Introduction The Browser AI API is a proposal for a new browser feature that makes AI models accessible directly on users' devices through the browser. By offering a simple API available on the...
elements
As much as I struggle with on-device processing and the quality of its output compared to server models, I am excited by some of the APIs that are being built into browsers that are backed by LLMs and other AI inference models. For example, the prompt API, along with a multi-modal version that can take any arbitrary combination of text, image, and audio and run prompts against them. These APIs are neat but not yet web-exposed and many developers struggle to know what to do with a generic prompt. It’s not a solution that is natural to many people yet.
Faces: Slides worth presenting
Faces is the AI presentation tool where every slide uses the full power of the web.
Zain Shah on Twitter / X
Imagine every pixel on your screen, streamed live directly from a model. No HTML, no layout engine, no code. Just exactly what you want to see.@eddiejiao_obj, @drewocarr and I built a prototype to see how this could actually work, and set out to make it real. We're calling it… pic.twitter.com/C4BEi1lse8— Zain Shah (@zan2434) April 22, 2026
Video Player
A composable, shadcn/ui styled video player component that uses the media-chrome library.
WebVR - virtual reality in your browsers
Slides for my Talk about WebVR. Presented at BED-Con in Berlin 2016 (http://bed-con.org/2016/)
Client Side of なんちゃらfresh.tv
High Performance Browser Networking (O'Reilly)
What every web developer must know about mobile networks, protocols, and APIs provided by browser to deliver the best user experience.
Zain Shah (@zan2434)
Imagine every pixel on your screen, streamed live directly from a model. No HTML, no layout engine, no code. Just exactly what you want to see. @eddiejiao_obj, @drewocarr and I built a prototype to see how this could actually work, and set out to make it real. We're calling it Flipbook. (1/5)
HazAT/glimpse
Native micro Web UI for scripts and agents — super fast OS native webview with bidirectional JSON communication for agents
Web Components - Web APIs | MDN
Web Components is a suite of different technologies allowing you to create reusable custom elements — with their functionality encapsulated away from the rest of your code — and utilize them in your web apps.
Group Note Draft: Web User Agents
Web user agents include both web browsers and other intermediaries between end-users and the web.
This month in Servo: new webview API, relative colors, canvas buffs, and more! - Servo aims to empower developers with a lightweight, high-performance alternative for embedding web technologies in applications.
Servo is becoming truly embeddable this year.
