this happens with getClient and setClient because it is a svelte context which is only available at component initialization (construction) and cannot be in an event handler.

It's more powerful to have them happen in definition order, because this lets you intercept thing in event handlers or in actions.

For example, an event handler callback that can be used to handle both fullscreenchange and fullscreenerror might look like this:

Handlers are normally not suffixed, but instead, they most often have on as the prefix (onClick, onSwipe etc.).

Event listener and event handler are two terms that cause confusion.

A listener watches for an event to be fired. For example, a KeyListener waits for KeyEvents, a MessageListener waits for messages to arrive on a queue and so on. The handler is responsible for dealing with the event. Normally, listeners and handlers go hand-in-hand. For example, the KeyListener tells the ExitHandler that "the letter Q was pressed" and the handler performs logic such as cleaning up resources and exiting the application gracefully. Similary a ButtonClickListener would tell the same ExitHandler that the "Exit button was clicked". So, in this case you have two different events, two different listeners but a single handler.

The most basic difference is the association Listener is associated with Event Source (Ex: key board) Handler is associated with an Event (Ex: keydown)