Hot Topics Panel
summary
Panel debates concrete outcomes: vendors abused prefixes and left site CSS broken, so browsers put experimental features behind a flag in Canary; community groups and appcache prototypes produce usable demos but often become costly polyfills like the polyfill that disabled zoom which fixed Safari's orientation bug but drained battery; packaging proposals aim for offline installable web apps without losing URLs; Chrome creates a Blink fork of WebKit to restore engine diversity; responsive images and bandwidth detection remain unsolved engineering problems.
AI-written summary · about
chapters (18)
- 0:00Hot Topics Panel intro
- 1:30Not the browser panel
- 3:42Apple and web standards
- 6:32W3C vs WHATWG
- 11:58Browsers and standards
- 13:42Vendor prefixes rise and fall
- 17:57Polyfills vs prefixes
- 23:21Polyfills necessity
- 28:36Google Gears success
- 31:06Device APIs security
- 33:35Installable web apps
- 37:53Modern web packaging
- 41:04WebKit to Blink
- 45:38Responsive images
- 46:39When problems aren't our problems to fix
- 49:07IE6 problem?
- 51:14Simplifying vs over-engineering
- 53:40Closing remarks
