Spxg
Spxg
> We don't have to think about wasm each time we add a test function (only when we add a test module)... done
hmm, `continuous-integration/appveyor/pr` failure doesn't seem related to this PR
```rust #[cfg(not(all(target_family = "wasm", target_os = "unknown")))] #[deprecated(since = "0.33.0", note = "use trace_v2 instead")] pub fn trace(&mut self, trace_fn: Option) {} #[cfg(not(all(target_family = "wasm", target_os = "unknown")))] #[deprecated(since =...
This change doesn't break existing functionality when `WASM_BINDGEN_TEST_ADDRESS` isn't set, so LGTM. PRs are welcome!
> happy to submit a small PR welcome!
wasm-bindgen version? Do `put_image_data` interact with the wasm and js array? This issue has been fixed in the recent version.
Do you have backtrace and reproducible example?
I'm not sure if it's the same issue: https://github.com/wasm-bindgen/wasm-bindgen/pull/4622
A reproducible example is: ```rust #[cfg(test)] mod tests { use wasm_bindgen::{Clamped, JsValue}; use wasm_bindgen_test::wasm_bindgen_test; wasm_bindgen_test::wasm_bindgen_test_configure!(run_in_browser); #[wasm_bindgen_test] fn detached() { let buf = vec![1, 2, 3, 255]; let image_data = web_sys::ImageData::new_with_u8_clamped_array(Clamped(&buf),...
```js const originalArray = new Uint8ClampedArray([255, 0, 0, 255, 0, 255, 0, 255]); const imageData = new ImageData(originalArray, 2, 1); console.log(imageData.data[0]); originalArray[0] = 123; console.log(originalArray[0]); console.log(imageData.data[0]); // output: 255 123...