Andre-Philippe Paquet

@PedroRestrepo I see you are using React 17. I had similar out-of-sync / jumping cursors issues on iOS using React 17 and reverting to React 16 fixed it. My hunch...

> Generally speaking, I am a tad scared of adding this feature. > > With your change the sync should still occur when the File is dropped as believe. The...

Alright. Let me know if you need my help testing anything on mac. I'm on Discord too if you want to ping me there.

Good thread on the fsync problem on MacOS here: https://twitter.com/marcan42/status/1494213855387734019?s=21

I'm also interested in this. I also had a similar issue dealing with a `Vec` and a `Reader` inside the same struct, with the `Reader` referencing the `Vec`. I solved...

It seems like I was wrong on the origin of the problem in yamux's commit history. I've narrowed the problem to https://github.com/libp2p/rust-yamux/pull/112 It seems like the issue comes from not...

> Thanks for further bisecting this issue! > > > Perhaps I'm wrong, but it seems like [flushing in frame::Io](https://github.com/libp2p/rust-yamux/blob/24d5464b25c938b786519f75064e8a81f0b3d80d/src/frame/io.rs#L119) polls to send the remaining frame. If sending cannot be...

Ok, I think I got it. The issue seems to really be in yamux, and is indeed related to improper flushing. In the `next()` method's loop, a frame could be...

A bit more digging... Writing to websocket (wasm-ext) may lead to `Pending` if another frame is being sent (see [this](https://github.com/libp2p/rust-libp2p/blob/96dbfcd1ade6de5b4ae623f59fb0d67b2916576a/transports/wasm-ext/src/lib.rs#L485)). Noise implementation can write pending frame on flush (see [this](https://github.com/libp2p/rust-libp2p/blob/b79fd02f0bdde07f437c691e278a16cf9024036a/transports/noise/src/io.rs#L138))....

> I am not yet sure whether we should extend `next_frame`, or should introduce a forth future `next_flush`. That's what I thought I would do at first, but polling the...