Naming convention for on directive custom events

[S1r-Lanzelot]

A "custom event to do stuff" off the on directive seems like it should be named customeventtodostuff instead of customEventToDoStuff; even though on:customeventtodostuff (and even worse, oncustomeventtodostuff) makes my eyes bleed. What is the rational for the naming of on events and should custom events follow the convention? If this is documented somewhere I would appreciate a reference.

Thank you.

[brunnerh]

The reason is that properties for these events really exist on elements, so adding an event that way is analogous to just setting those properties.

Event handlers are exposed in two ways.

The first way, common to all event handlers, is as an event handler IDL attribute.

The second way is as an event handler content attribute. Event handlers on HTML elements and some of the event handlers on Window objects are exposed in this way.

(See e.g. the interface for GlobalEventHandlers which are implemented by HTMLElement.)

Using properties instead of the special on: syntax allows event handlers to be spread in components like any other property. This is helpful for forwarding all events (see #2837).

I don't think you have to follow the convention for component events; an exception might be forwarding existing DOM events.