Becoming Responsible for CSS
summary
Work on CSS moves from vague goals to concrete actions: publish bugs with W3C-style tests, vote for browser feature bugs, and measure polyfill costs — one Chrome polyfill spends 20% of time just handling string values. Examples include pushing CSS Shapes through bugs and experiments, documenting issues that improve the grid spec, and building Houdini hooks like a typed object model and custom paint so JavaScript prototypes can prove whether a feature deserves standardization.
AI-written summary · about
chapters (18)
- 0:00Intro
- 3:25Write
- 3:50Web Fonts
- 4:25Bootstrap
- 4:55Article
- 5:45Solution
- 6:20Rachel Andrew
- 7:00Twitter
- 7:30Discourse
- 8:05Shout
- 8:40W3C
- 9:10Test the Web Forward
- 10:15Browser Bugs
- 11:00Browser Selector
- 12:15Houdini
- 13:10Polyfills
- 15:00Box Model
- 15:40JavaScript
