Lukas Potthast

Thank you! I totally missed that... That works great. Close the issue if you want. One downside I see is that, if accessed multiple times, you either have to `unwrap_or(...)`...

1.0 does not work unfortunately. `time` is guarded by the 'std' feature. This means that I have to disable std in order to run on wasm. But I do need...

+1, currently using a (kind of hacked-together) fork (https://github.com/thedodd/trunk/compare/master...murosuke:trunk:develop) for this. @thedodd It would be really nice if this could be merged and released. Update: https://github.com/thedodd/trunk/pull/532 was merged into trunk-ng....

Looks promising. It would be great to see these commits upstreamed to this crate!

A not-so-great workaround would be to add a “pre-build” hook that executes a `cargo check` to enforce running the build once.

I am seeing floating point values in Chrome. Check out https://react-spectrum.adobe.com/react-aria/useMove.html (end of page, dragging the knob should show non-integer values coming from `MouseEvent.page_x()` and `MouseEvent.page_y()` respectively).

I'm currently seeing floating point values on: MacOS Sonoma v14.2.1 with Chrome Version 122.0.6261.112 (arm64) Saw the same behavior on my Linux desktop (OpenSUSE Tumbleweed, up-to-date Chrome as well) Sure,...

> Whats your [`Window.devicePixelRatio`](https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio)? `2` on 100% window scaling.

Ran into the same issue. This is still an issue with the latest `beta3` release.

I would also love to have the flexibility of this request. Using `strip_option` really limits your users, which I would really like to avoid to in my case. (The same...