Interoperable Component Patterns
summary
Conference survey shows ~2,000 responses and the talk makes concrete interoperability choices: use custom elements via a polyfill (recommends x-tag polyfill over experimental Polymer), pass data as attributes then deserialize into properties, communicate back with DOM events (use CustomEvent detail for payloads), avoid early-stage Shadow DOM and rely on patterns that work back to IE9. A working prototype publishes Ember components as custom elements so they render from plain HTML across frameworks and environments.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:40Who am I
- 1:25Emperor Community Survey
- 2:24Architecture
- 3:05Design
- 6:52Custom Elements
- 9:33Passing Attributes
- 10:29HTML Declaration
- 11:20HTML Hidden
- 14:06Component Properties
- 15:25Component Consumer
- 17:18Deserialization
- 18:21Communication with Events
- 18:35React
- 21:13Events
- 21:41Why Events
- 24:39Consumer Concerns
- 26:14Practical Recommendations
- 26:52Document
- 27:07Shadow DOM
- 27:41Experiment
- 28:14Event Handling
- 28:56Element Modifier
- 30:15Prototype
- 31:22Whoops
- 31:48TillDays
- 32:02Raymer
- 32:13Page
