Checkbox onChange event called before value updated

[T-bond]

What package has an issue

@svelteuidev/core

A clear and concise description of what the bug is

Checkbox event callbacks do not keep order.
Binding a change event handler after the value binding will call the change event before the value update event.
In plain Svelte order of attributes are kept.

Related: #277

In which browser(s) did the problem occur?

Microsoft Edge

Steps To Reproduce

See sample code:

<input type="checkbox" on:change={() => console.log('Svelte before change', val)} bind:checked={val} on:change={() => console.log('Svelte after change', val)} />
{val}
<Checkbox on:change={() => console.log('SvelteUI before change', val2)} bind:checked={val2} on:change={() => console.log('SvelteUI after change', val2)} />
{val2}

Do you know how to fix the issue

No

Are you willing to participate in fixing this issue and create a pull request with the fix

No

Relevant Assets

[BeeMargarida]

From a first glance, this has to do with our current logic of event forwarding in components.
However, I don't think this is fixable right now, even making a simple event forwarding for the on:change like they it shows in the Svelte docs - https://svelte.dev/tutorial/event-forwarding - this is not possible.
As anyone have any idea of a solution?

[BeeMargarida]

I'm gonna create an issue on Svelte side so that this can be discussed. It seems like a very specific edge case, but it's interesting. I'll tag you

[BeeMargarida]

Gonna close this issue since it can be considered expected behaviour