Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Safari on Mac: OnMouseUp not firing in Safari when opening a select dropdown so Fit.Events.GetPointerState() returns incorrect mouse button state #163

Open
FlowIT-JIT opened this issue May 11, 2022 · 1 comment

Comments

@FlowIT-JIT
Copy link
Collaborator

Invoking Fit.Events.GetPointerState() after opening a <select> dropdown control using the mouse on Safari on Mac, will incorrectly indicate that the primary mouse button is still being held down, because Safari doesn't fire OnMouseUp once the button is released, making it impossible to detect the correct state. The state is fixed once the user clicks somewhere else in the web application.

@FlowIT-JIT FlowIT-JIT changed the title Safari on Mac: MouseUp does not fire in Safari when opening a native dropdown control so Fit.Events.GetPointerState() returns incorrect mouse button state Safari on Mac: OnMouseUp not firing in Safari when opening a select dropdown so Fit.Events.GetPointerState() returns incorrect mouse button state May 11, 2022
@FlowIT-JIT
Copy link
Collaborator Author

Possible "fix" for Safari on Mac: Detect that MouseDown happens on a element and reset the Primary property (Fit.Events.GetPointerState().Buttons.Primary) postponed using setTimeout(..., 0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant