Web Components
summary
Chrome Canary requires enabling flags and the polyl polyfill to exercise Shadow DOM, CSS Variables, Regions and custom filters; the implementation is Chrome‑only and hard to debug. Concrete demos show custom elements with lifecycle callbacks, regions flowing content into named containers, CSS vars scoped by selector, shaders applied via a filter URL and live text preserved. Several features fail or are incomplete (animations, @font‑face, accessibility) so experiments work but are not production ready.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:02Messy web development solution
- 3:49Chrome Canary setup
- 4:32Core specs
- 6:16Custom elements
- 8:06CSS Regions integration
- 12:07CSS Variables role
- 14:15Custom Filters effects
- 16:44Reusing components
- 19:18Shadow DOM styling limits
- 20:42Resources and communities
- 21:46Test the Web Forward call
- 22:23Q&A
related talks
32mFuture CSS in Web Components
42mThe Good, The Bad, The Web Components
42mWeb components and the future of web development
16mWeb Components
24mWeb Components: It's all rainbows and unicorns! Is it?
39mWeb components - A whirlwind tour
51mCSS in 2023 and beyond
36mWeb components - A whirlwind tour thru the future of the web
