Emily

@zamotany Thanks for all the work you’ve put into this! I’ve taken a look and I think the changes to RN core make sense to me, and I think we're...

@zamotany So am I understanding correctly that you only need the first 2 PRs to support your use case? If that's true, then I don't think there's any reason to...

I'm investigating an issue that sounds like it might be similar, but I'm not sure if it's exactly the same - what I'm observing is that double tap will focus...

Adding the people who have contributed to this proposal/discussion at FB: @shergin, @RSNara, @mhorowitz @fkgozali And some people who might be interested: @vmoroz @acoates-ms This proposal isn't something we're completely...

@dvicory Thanks for your comment! That use case is definitely one we want to support - we need to be able to synchronously call into JS (and get a return...

> The inefficiency of sync calls: I am not sure I explicitly mentioned that, I am proposing that RuntimeExecutor might call the callback synchronously if it believes it's the most...

@grabbou: > I guess my main question is what is wrong/no-go with current architecture that would require a whole new set of classes and abstractions? I would say accessing JSExecutor...

@mhorowitz I think you're right - we're conflating (at least) two different things here. The API that we expose to third party developers that want to add support for a...

@jbrodriguez No updates at the moment, I'm still tinkering with this to find the right API for what we need. This proposal isn't blocking any work on Fabric or TurboModules,...