Andreas Monitzer

Is there some kind of quick fix that can be applied until the real fix is implemented?

> Maybe @anlumo could try to integrate this into his release last minute. jk _scnr_ We've already fixed the issue by switching to [geo-clipper](https://crates.io/crates/geo-clipper), which is pretty much a drop-in...

It feels faster than geo-booleanop, although that might be related to the C++-library being built with optimizations even for Rust debug builds. I don't have any objective numbers, though.

Has there been any progress on this issue in the last 3 months?

The current design also doesn't allow writing independent components that are added to a web application, since there's no guarantee that it's the only component using raw-window-handle, and thus the...

> For what it's worth, the reasoning for the current API is discussed in [#26 (comment)](https://github.com/rust-windowing/raw-window-handle/pull/26#discussion_r325860649) mentions some of the downsides of exposing web_sys types directly That's from before OffscreenCanvas...

I can see the issue with emscripten, but how does creating it in JavaScript cause issues? You can simply pass it to a wasm function call and wasm-bindgen will wrap...

It might not be in the DOM though, or even a DOM element in the first place (OffscreenCanvas). A solution might be to make `WebWindowHandle` an enum with three variants:...

Well, you *could* rely on the [IntoWasmAbi](https://docs.rs/wasm-bindgen/latest/wasm_bindgen/convert/trait.IntoWasmAbi.html) and [FromWasmAbi](https://docs.rs/wasm-bindgen/latest/wasm_bindgen/convert/trait.FromWasmAbi.html) traits to just store a `u32` for the `JsValue`, but this requires some pretty unsanitary and `unsafe` code on the implementor...

A collision-free id could be generated by `self.crypto.randomUUID()` ([documentation](https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID)), it just needs to be a string instead of a u32 (a u128 would also work technically, but then you'd have...