Chris Cowan
Chris Cowan
Emscripten uses shared memory for thread support in WebAssembly using web workers. Each worker/thread keeps the shadow stack in a different region of the shared memory. A pointer to the...
Here's two existing threads on the subject: https://github.com/WebAssembly/design/issues/1271 and https://github.com/WebAssembly/design/issues/1210. They seem to address an equivalent proposal and a few others.
What actually happens right now (or is supposed to happen) if a Javascript thread takes a reference to a WASM memory's ArrayBuffer and is reading/writing to it while a separate...
> because react-dnd will just treat my non-react draggable element as a native draggable Are those terms not synonymous here?
Oh, the issue is that I only needed and tested that this allows files to be dragged into the browser onto non-React-DnD dropzones. I didn't test draggable non-React-DnD elements. More...
I think merging my fork would make sense if the issue @fixpunkt brought up was fixed: my fork leaves non-DnD draggable items broken.
The bug still exists in v5.5.0. Adding `strip_root=true` to the [options] of a fresh or existing project reliably triggers it for me. Does it not for anyone else? I've attached...