ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Pressing ctrl key on the keyboard prevents mouseUp events from happening

more options

We are using react and listening to mouse events (up, down, move...). While dragging with the mouse (So mouse down and then mouse move) if we press the control key on a Mac keyboard and then release the mouse, the "mouseUp" event is not fired.

We are using react and listening to mouse events (up, down, move...). While dragging with the mouse (So mouse down and then mouse move) if we press the control key on a Mac keyboard and then release the mouse, the "mouseUp" event is not fired.

الحل المُختار

I'm sorry this is no bug from Firefox, the issue was that we were only listening to the left mouse button (so mouseEvent.button = 0) while once we press ctrl key, the mouseUp event will get a button code 2. I'm closing this issue

Read this answer in context 👍 0

All Replies (5)

more options

This is probably worth submitting to bugzilla as a bug, I didn't see anything like it when I looked:

https://bugzilla.mozilla.org

more options

Thank you I just submitted it there https://bugzilla.mozilla.org/show_bug.cgi?id=1614951

more options

You could provide more detail in the bug report as you didn't mention using React or possibly add a test page to the bug report. Someone needs to be able to reproduce this issue.

I'm curious why you are pressing the Ctrl key.

Is the Ctrl key the only modifier key that gives problems ?

more options

Yes it's only the ctrl key that causes this. We are using the press on this key to modify the drag behaviour. Example: moving an element in the canvas with the drag would snap to some certain grid, and if you press the ctrl key while doing that then we skip the snapping. I cannot really provide a test page but you're right I will mention that we're using react.

more options

الحل المُختار

I'm sorry this is no bug from Firefox, the issue was that we were only listening to the left mouse button (so mouseEvent.button = 0) while once we press ctrl key, the mouseUp event will get a button code 2. I'm closing this issue