Jonathan Böcker

Thanks a lot for the update. Are you referring to https://dart-review.googlesource.com/c/sdk/+/253000/ ? Great work, I saw you landed a few others as well. I look forward to not working around...

I pulled from Flutter `master` release: ``` Flutter 3.1.0-0.0.pre.2032 • channel master • https://github.com/flutter/flutter.git Framework • revision 195fa0b728 (2 hours ago) • 2022-08-02 05:39:06 -0400 Engine • revision 4b19256979 Tools...

This might not help you @srujzs, but I've worked around the problem by [creating a wrapper/proxy class](https://github.com/Schwusch/dart_js_bug_repro/commit/5fd00509a85f5e89fdf415ff69bdd5ea091523e9) for the static interop code. That fixes hot restart in the GUI code...

I now noticed the wrapper/proxy solution actually broke the functionality, since the callback is no longer called. Maybe the closure passed to `allowInterop` broke because of it?

Nice 🙂 I guess that solves #25

Hi! Thank you for the feedback. It seems like this appear in a couple of scenarios, like scrolling/navigation, and is not correct until something else triggers a repaint. Usually user...

Does either fix work on its own or is both needed? Both are potentially expensive, but if there's no other way...

Hi, I suspect it has to do with what @nezoat points out in #5. I don't have much time to work on this, though I am open to PRs!

Hi @nezoat! I am not sure I understand the use case, would you mind expanding a bit on how to retrieve the ancestor? Would it be an argument to `ArrowContainer`...

Hi, I just checked with latest on master, and it seems to be working in all the use cases I have, thank you 🙏 I'd say this issue is resolved....