为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

定位到答案原位置 👍 0

所有回复 (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