Best results in other decks

Event listeners are called in the order of their registration: button.addEventListener('click', () => console.log("I run first")) button.addEventListener('click', () => console.log("I run second")) Sometimes you want a listener to always run...

...first (or last), but have no control over the order in which other listeners are registered. There is no clean mechanism in the DOM API for this. This card shows...

config.before(:suite) { puts 'BEFORE :suite' } config.after(:suite) { puts 'AFTER :suite' } end describe 'order of hook execution' do around(:all) do |each| puts 'AROUND BEFORE :all' each.run puts 'AROUND...