"Doing The Unstuck"
summary
Explains concrete web-compat fixes: renaming a conflicting Mootools method to string.prototype.includes to avoid breaking sites, solving array prototype collisions and the SpiderMonkey array.prototype.values bug with the unscopables hack, reverse‑engineering Apple’s window.orientation for interoperable DOM behavior, implementing WebKit CSS prefixes (webkit-background-clip:text) across engines, noting removal risks like showModalDialog and AppCache, and running webcompat.com plus browser dev-channel testing and bug reports to diagnose and fix real broken sites.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 1:10Web compatibility explained
- 4:21JavaScript prototype conflicts
- 10:28DOM and proprietary APIs
- 15:24CSS and vendor prefixes
- 21:50Standardizing non-standard features
- 23:56Removing deprecated web features
- 24:59How developers can help
- 27:47Q&A and closing remarks
related talks
54mHot Topics Panel
43mResponsive, Adaptive and Responsible
58mSquashing JavaScript bugs
44mAdvancing the web without breaking it?
28mLet's Save The Internet
43mPanel Discussion: How Web Developers are Changing Web...
44mBattling Browser Bugs for "Fun" and (Non-)Profit
34mPanel: Don't Break the Web! - Evolving JS While Keeping Developers Sane
