Alexander Prinzhorn

I agree that there needs to be a way to get back into the "nothing is selected" state using a keyboard. A keyboard equivalent to hitting the "X". But maybe...

Currently ESC does nothing when the dropdown is already closed. For a Chrome user at least this is unexpected ux, because the X on the right makes it look like...

Oh neat. I'm not sure when I could look into this, I'll post here if I do to avoid double work. I personally would give `--namesite` precedence over `--idsite`. But...

I wouldn't deprecated the current API because your design suffers from one limitation: you can only get a single reference to each of the things. But there are pre-processors that...

> ```svelte > on:destroy={localHandler} > on:destroy={preprocessorHandler} > on:destroy > bind:props={localProps} > bind:props={preprocessorPropVar}/> > ``` This is not valid. I don't know what parser Svelte uses, but none of `setAttribute`, `getAttribute`...

First of all a big thumbs up for declarative actions. When I first started using Svelte and wrote my first action I thought "amazing, this is my interface into the...

> One open question for me is how to make this composable. Right now you can mix and match actions to your liking If declarative actions are compiled to the...

> A declarative action would be usable with `use` or as regular ol' function? Yes. If you currently `import Foo from Foo.svelte` you get a constructor and can do either...

> What about actions without a script at all? Good point, maybe the existence of `` triggers it, because that's what an action requires. It's the point of an action....

> What's stopping us from allowing multiple props, like in a Component, and then compiling them into a single function parameter? This could be less intuitive then just forcing actions...