mc1098

So I have been thinking about this and toying around in a local branch about a solution. ## NewType Events vs Event Name Trait One decision is whether to have...

> In discussion with colleagues, someone referred to this SO thread, which seems to be addressed in the 0.8 fix: It is the change from #389 and your colleague is...

Ok, so with some more investigation - I found another bug of a _similar_ type (do you want a new issue for this?) and I think this has got me...

> Sycamore already does something very similar. The problem is that the event handlers are tied to the reactive scope, otherwise the handler couldn't possibly reference reactive variables from the...

> The problem with calling remove_event_listener is that every time a node is removed, we must make an additional call to js which would not have been there before. I'm...

> straightforward: passing props. Using a context if the descendants can be too deep down the tree. You may find that #905 is related to this topic too.

Hi @nbrr, I've been looking at this issue, btw thank you for the example repo made it easy to do :) I'm not experiencing any problems or differences between the...

Unblocking this issue and marking the feature as accepted. I agree with @siku2 that being nightly provides an opt-in behaviour and allows us to start building up lints. Once the...

For a `NodeRef` version I first thought of something like this: ```rust pub fn attach_event_listener( &self, event: S, callback: Callback, ) -> Option where S: Into { let passive =...

Sorry for the accidental closing 😢