Klemen Slavič

Right, good point, I was looking at the wrong type. Where would that belong if I were to submit a PR for this here? I couldn't find any JSX type...

The problem with deferred events in my case is that I rely on stopping propagation on components (like ``) that should prevent ancestor event handlers from receiving events. In Solid's...

~It looks like this example worked as expected with Solid 1.0.0, but it doesn't work in 1.3.3 at least:~ Actually, I tried rolling back to Solid 1.0.0 as that was...

Same thing in the playground: https://playground.solidjs.com/?hash=1871281921&version=1.3.3 I might just be misunderstanding how interop code should work with Solid's delegated events, but I would expect being able to stop propagation at...

Yeah, I tend to work on systems that need to play nice with other legacy components, so relying on precise DOM event binding is key here. I don't mind opting...

So should I close this issue and write up a PR per @otonashixav's [comment](https://github.com/otonashixav) on `dom-expressions`? I don't mind doing the legwork, I just need a bit of guidance to...

I would definitely like the documentation and tools to describe what the idiomatic way of opting into/out of delegated events would look like in Solid, and if there is delegation...

After reading this issue, I've started facepalming at my decision to go with mdl on a personal project. :/ I love how Google loves starting and torching projects even they...

Yeah, am having the same experience with IE11 on this issue. Will try to see if I can get it to give up a specific case where this is consistently...

OK, found a workaround for this issue if it helps debugging: https://jsfiddle.net/pzaafu34/ The relevant bit is: ```jsx this._portal = ref}> ``` For some reason, the reference assignment prevents the node...