The listeners keep firing.
A Melbourne practice that reads event listener activity in applications — attach points, fire order, leaks, and the quiet second handler nobody budgeted for.
Morning at Level 7, 84 William Street, Melbourne VIC 3000 often starts with a printed trace and a mug ring on the margin. Listener Vertex Grid is an application analytics practice with one narrow subject: event listener activity. We do not sell a screen you log into. We sit with the people who own the application, watch how listeners attach and fire, and write an account the team can act on.
The work is slow on purpose. A listener that fires twice is rarely a mystery once someone names both attach points. A scroll handler that never detaches is rarely a debate once the page that created it is put next to the page that forgot it. Teams in Melbourne and further afield bring us the application, the symptoms, and whatever traces they already have. We return a fire-order map, a leak list, and a walkthrough — then we leave the application in their hands.
Listener work, named plainly
Each engagement is a sitting, a reading of traces, and a written account of how event listeners attach, fire, and linger in an application. Nothing here is a product you log into.
Event listener activity analysis
A contained sitting that maps how listeners attach, fire, and linger in one application, then writes the findings in language the owning team can use.
From AUD 8,400 for a contained pass; quoted for larger estates
Listener inventory
A catalogue of attach points across named surfaces, so the team can see what is listening before anyone argues about a single click.
From AUD 3,600
Incident reconstruction
A forensic sitting after a failure involving handlers — double submit, a frozen page, a modal that would not close — written up for the people who have to explain it.
From AUD 4,200
Pre-release listener pass
A timed reading of event listener activity on the surfaces about to go public, with a short note on what should be detached before the date.
From AUD 6,800They found the second click handler on the enrolment button — the one registered in a layout the product team no longer opened.
Recent notes
When a click handler fires twice and nobody saw the second attach
A Melbourne enrolment form posted two records because a retired campaign layout still registered a click. The second attach was not on the button anyone was looking at.
Detach is not the same as “we stopped listening”
Teams often remove a widget and assume its listeners have gone with it. Route changes in an application are where that assumption most often fails.
Reading scroll listeners without drowning in the trace
Scroll and resize handlers fill a trace quickly. A Melbourne sitting stays useful when we name the surface first and only then sample the fire.