Should event-listeners stop executing code?

[Falke-Design]

Checklist

• [X] I've looked at the documentation to make sure the behavior isn't documented and expected.
• [X] I'm sure this is an issue with Leaflet, not with my app or other dependencies (Angular, Cordova, React, etc.).
• [X] I've searched through the current issues to make sure this hasn't been reported yet.
• [X] I agree to follow the Code of Conduct that this project adheres to.

Steps to reproduce

If we fire a event, the code after fireing will be not executed, if the listener throws an error:

map.on('customEvent',()=>{
    throw new Error(`I don't like that event!`)
})

function fireSomeEvent() {
    console.log('Some task ...')

    map.fire('customEvent');

    console.log('Another task ...')
}
fireSomeEvent()

Expected behavior

I'm not sure about what is right, but I have expected that the fireSomeEvent function will not break and continue executing.

Current behavior

fireSomeEvent function breaks after an Error is thrown in the listener of the fired event

Minimal example reproducing the issue

https://plnkr.co/edit/apIUNihbz3VCAAia

Environment

• Leaflet version: 1.9.4
• Browser (with version): Firefox
• OS/Platform (with version): Windows 10

[IvanSanchez]

Compare with the behaviour of the built-in EventTarget:

const foo = new EventTarget();

foo.addEventListener('customEvent',()=>{
    throw new Error(`I don't like that event!`)
})

function fireSomeEvent() {
    console.log('Some task ...')

    const ev = new CustomEvent('customEvent');
    foo.dispatchEvent(ev);

    console.log('Another task ...')
}
fireSomeEvent()

This will log "Another task".

We never really set the Leaflet Evented behaviour on stone, but I guess that @Falke-Design is right - the behaviour is not as expected (since I'd expect the same behaviour than EventTarget).

I'd even say "let's replace Evented with a subclass of EventTarget", since it's 2024 and all browsers implement it.