Hitchhiker's Guide to Web Standards
summary
Explains how web APIs get specified and shipped: uses WHATWG repos and Web IDL, edits specs as source files on GitHub, files issues on freenode/IRC and lands patches in Chromium. Claims concrete wins: implemented referrerpolicy attribute, changed fetch credential behavior in Chrome, and priority hints resource API exists as an experimental implementation. Shows how to read algorithms and IDL so calls either convert or throw, and how to find good‑first issues to contribute.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 1:01Goals
- 1:51Setting the Stage
- 2:05Definition
- 3:18Web Tech
- 3:53Web API
- 4:23Where Web APIs come from
- 4:51What is JavaScript
- 5:27EquiScript
- 6:20Web APIs
- 7:14The What Working Group
- 7:29The Web Platform
- 7:58JavaScript Engine
- 8:20DOM
- 8:34Network
- 9:17Anatomy
- 9:36Algorithms
- 10:08Console Count
- 10:56Look Feel
- 12:53How Web IDL Works
- 13:07Web IDL Sheriff
- 13:38Web Sheriff
- 14:55Why WebIDL
- 15:09What WebIDL Does
- 16:19How I Got Involved
- 17:30Dominic Farolino
- 18:10What Working Groups
- 20:49Working Group
- 21:30Why do this
- 22:10CascadiaJS Repository
- 22:46Fetch API
- 23:08referrer policy
- 23:21console API
- 23:34priority hints
related talks
31mEvolution Of The Web
12mSpec-Tacular Streaming: Lessons Learned in Standards Land
32m📗 Web standard consortiums are a game with Chrome as the monopoly man
26mWhat is/Who Makes "The Platform"
48mWhose web is it anyway?
30mChrome and the Web
36mInto the web multiverse
42mThe Hitchhiker's Guide to Client-Side Security