Skip to content

web: window cursor position is set on mouse click #7513

Closed

Description

@rparrett

Bevy version

main

Relevant system information

AdapterInfo { name: "ANGLE (Apple, Apple M1 Max, OpenGL 4.1)", vendor: 4203, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Gl }

chrome, firefox, safari

What you did

(with wasm-server-runner)
cargo run --example 3d_scene --target=wasm32-unknown-unknown

Open javascript console, click canvas, observe error message

What went wrong

ERROR crates/bevy_winit/src/system.rs:182 could not set cursor position: NotSupported(NotSupportedError)

Additional information

This seems sort of harmless, but is very strange.

Doesn't happen in native builds on MacOS, but it seems worth testing other platforms.

Activity

  1. added
    C-BugAn unexpected or incorrect behavior
    S-Needs-TriageThis issue needs to be labelled
    on Feb 5, 2023
  2. tim-blackbird commented on Feb 5, 2023

    @tim-blackbird
    Contributor

    I think it's the same issue as #7377. Clicking triggers change detection just like the scale_factor_override example does.

    I'll get back to work on my PR to fix it. Lost some motivation as it ended up needing more changes than I thought :v

  3. hankjordan commented on Feb 6, 2023

    @hankjordan
    Contributor

    Closing as duplicate, feel free to re-open if it isn't fixed by #7517

  4. added
    A-InputPlayer input via keyboard, mouse, gamepad, and more
    O-WebSpecific to web (WASM) builds
    and removed
    S-Needs-TriageThis issue needs to be labelled
    on Feb 6, 2023
  5. rparrett commented on Feb 6, 2023

    @rparrett
    ContributorAuthor

    I am not really seeing the harm in leaving this open until closed automatically by that PR, as it's tracking a unique platform-specific behavior not really covered by the other issue text.

    But I guess it can stay closed because this is definitely fixed by that PR and it seems likely to be merged.

  6. hankjordan commented on Feb 6, 2023

    @hankjordan
    Contributor

    I am not really seeing the harm in leaving this open until closed automatically by that PR, as it's tracking a unique platform-specific behavior not really covered by the other issue text.

    But I guess it can stay closed because this is definitely fixed by that PR and it seems likely to be merged.

    Ah, my mistake - reopening.

  7. added a commit that references this issue on Feb 7, 2023
    f69f132
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-InputPlayer input via keyboard, mouse, gamepad, and moreC-BugAn unexpected or incorrect behaviorO-WebSpecific to web (WASM) builds

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions