Deep Dive on Ember Events
summary
A concrete rule: DOM listeners always fire first, so Ember's abstractions cannot stop propagation of native handlers. The Ember event dispatcher uses delegated handlers (in practice about ~32 delegated handlers for 10,000 components in a quick benchmark) via jQuery or the DOM API, trading memory for far fewer DOM listeners. Practical gotchas: element-modifier Ember actions do not receive the native event, stopping propagation must use bubbles=false or call stopPropagation on the DOM event, and switching one handler type can silently break a tooltip/tour flow.
AI-written summary · about
chapters (4)
related talks
24mNew to Ember: What ARE All These Things?
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
33mThe Observer tip-jar
26mBuilding Better Components
18mThe Main Event: Beyond Event Listeners in JavaScript
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
32mAn Animated Guide to Ember Internals
26mModern Javascript Frameworks - Introduction to Ember.JS and Ember-CLI