Web Platform and Browser APIs
Parent: JavaScript and Node.js · researched 2026-06-02T17:15:55.052Z· 5 sources · 12 concepts · skill web-platform-browser-apis
programming-languages hub reference for the browser-side JavaScript platform — the APIs that ship in the browser, not in the ECMAScript language (javascript-nodejs) or in Node. This is the half of "Ja
Web Platform & Browser APIs
- programming-languages hub reference for the browser-side JavaScript platform - the APIs that ship in the browser, not in the ECMAScript language (javascript-nodejs) or in Node. This is the half of "JavaScript" that lives between the language and the framework. Sibling to javascript-nodejs, javascript-runtimes-deno-bun-edge, and frontend-design. [source]
- TRIGGER: which browser API to use; DOM/events; the observer family; Fetch/Streams/abort; Web Components & Shadow DOM; Service Workers / offline / PWA; client-storage choice; real-time transports (WebSocket/WebRTC/WebTransport/SSE); View Transitions, Navigation API, WebGPU. [source]
- SKIP: JS language/runtime semantics → javascript-nodejs; non-Node runtimes → javascript-runtimes-deno-bun-edge; framework rendering (React/Vue/Svelte) → frontend-design / frontend-frameworks (concept-tree gap); CSS & visual design → frontend-design; Chrome-extension MV3 surfaces → chrome-dev. [source]
2026 frontier (confirmed current)
- Navigation API → Baseline Newly Available (Jan 2026) - Chrome, Edge, Firefox 147, Safari 26.2. The modern replacement for the History API: single navigate event, intercept + transition, proper SPA routing. Prefer it over history.pushState for new SPAs. [source]
- View Transitions API - same-document and cross-document; element-scoped transitions now enable targeted animations without animating the whole page. [source]
- WebGPU - in production browsers; 2026 is the consistency/predictability year. Compute + 3D; the successor to WebGL. [source]
- HTML-in-Canvas - render real DOM elements into a canvas (WebGL/WebGPU) while staying accessible, searchable, translatable. [source]
- Document Picture-in-Picture - always-on-top window with arbitrary HTML (Firefox 151 desktop + Chromium). [source]
- Soft Navigations API - brings Core Web Vitals measurement to SPA route changes. [source]
- Temporal (language, via javascript-nodejs) lands alongside as the modern date/time layer these APIs increasingly assume. [source]
Selection guidance
- One-way server push? SSE (EventSource) - simplest, auto-reconnect. Bidirectional low-latency? WebSocket. Media or P2P? WebRTC. HTTP/3 streams / unreliable datagrams? WebTransport. [source]
- Client storage: key/value tiny + sync → localStorage; structured/queryable/large → IndexedDB (via Dexie); HTTP responses → Cache API; real files / SQLite-in-browser → OPFS. [source]
- Watching layout/visibility? Use the matching observer, never a scroll/resize polling loop. [source]
- Encapsulated, framework-free widget? Custom Element + Shadow DOM. [source]
- CPU-heavy work? Web Worker (+ Atomics/SharedArrayBuffer for shared state); push to WASM if numeric. [source]
- SPA routing (new)? Navigation API + View Transitions, not history.pushState + manual diffing. [source]
Anti-patterns
- Polling scroll/resize/setInterval where an observer exists. [source]
- Assuming a Service Worker keeps in-memory state across events - it gets terminated. [source]
- Hand-rolling crypto instead of crypto.subtle; using Math.random() for tokens instead of crypto.getRandomValues/randomUUID. [source]
- Blocking the main thread with heavy compute instead of a Worker. [source]
- New SPA routing on the History API when the Navigation API is now Baseline. [source]
- Unbounded fetch with no AbortSignal.timeout() - leaks pending requests. [source]
Sources
- "New to the web platform in January / May 2026" - web.dev/blog [source]
- "Navigation API Reaches Baseline Newly Available" - InfoQ (May 2026) [source]
- "15 updates from Google I/O 2026 (Chrome)" - developer.chrome.com/blog/chrome-at-io26 [source]
- Microsoft Edge 147-149 web platform release notes - learn.microsoft.com [source]
- MDN Web Docs - Web APIs reference (canonical) [source]
Children
- DOM and Events (frontier)
- Fetch Streams and AbortController (frontier)
- Web Components and Shadow DOM (frontier)
- Service Workers and PWA (frontier)
- Client Storage (IndexedDB, Cache, OPFS) (frontier)
- Observer APIs (Intersection, Resize, Mutation, Performance) (frontier)
- Real-Time Transports (WebSocket, WebRTC, WebTransport, SSE) (frontier)
- Web Workers and SharedArrayBuffer (frontier)
- Web Crypto (frontier)
- Navigation API (frontier)
- View Transitions API (frontier)
- WebGPU and Canvas (frontier)
Frontier under this node: Client Storage (IndexedDB, Cache, OPFS), DOM and Events, Fetch Streams and AbortController, Navigation API, Observer APIs (Intersection, Resize, Mutation, Performance), Real-Time Transports (WebSocket, WebRTC, WebTransport, SSE), Service Workers and PWA, View Transitions API, Web Components and Shadow DOM, Web Crypto, Web Workers and SharedArrayBuffer, WebGPU and Canvas