Mouse Keys Left Click

In this chapter we’ll get into more details about mouse events and their properties.

• Mouse Keys Change Left Click
• Mouse Keys Left Click Windows 10
• Keyboard Shortcut Left Mouse Click
• Mouse Keys Left Click Not Working
• Left Click With Keyboard

Please note: such events may come not only from “mouse devices”, but are also from other devices, such as phones and tablets, where they are emulated for compatibility.

Mouse Keys Change Left Click

Hotkey for left mouse click I have Windows 10 on a desktop. I would like to set up a hotkey (CTRL+P) to be a left mouse click? This thread is locked. The keys that are involved in mouse keys are only the ones on the numerical keypad. 5 clicks the mouse, and the surrounding 8 numbers are used to move the cursor. / sets the 5 key to left click.-sets the 5 key to right click. sets the 5 key to left and right click simultaneously (useful for dropping an inventory of objects). This no longer works.

Step 1 Turn on MouseKeys in Windows XP by pressing “Left-Alt, 'Left-Shift' and 'NumLock” simultaneously. Press “Enter” to select “Yes” in the dialog box that appears to activate MouseKeys. Step 2 Move the mouse pointer left and right by pressing “4” and “6” on the numeric keypad. The actions for left/right mouse click depend on the program but generally: Left click – the normal or standard action. Left Click to select. Right click – additional or special options that apply to the selection. Right-click often makes a menu appear with choices that apply to the current selection or program.

Mouse event types

We’ve already seen some of these events:

mousedown/mouseup

Mouse button is clicked/released over an element.

mouseover/mouseout

Mouse pointer comes over/out from an element.

mousemove

Every mouse move over an element triggers that event.

click

Triggers after mousedown and then mouseup over the same element if the left mouse button was used.

dblclick

Triggers after two clicks on the same element within a short timeframe. Rarely used nowadays.

contextmenu

Triggers when the right mouse button is pressed. There are other ways to open a context menu, e.g. using a special keyboard key, it triggers in that case also, so it’s not exactly the mouse event.

…There are several other events too, we’ll cover them later.

Events order

As you can see from the list above, a user action may trigger multiple events.

For instance, a left-button click first triggers mousedown, when the button is pressed, then mouseup and click when it’s released.

In cases when a single action initiates multiple events, their order is fixed. That is, the handlers are called in the order mousedown → mouseup → click.

Click the button below and you’ll see the events. Try double-click too.

On the teststand below all mouse events are logged, and if there is more than a 1 second delay between them they are separated by a horizontal ruler.

Also we can see the button property that allows to detect the mouse button, it’s explained below.

Mouse button

Click-related events always have the button property, which allows to get the exact mouse button.

We usually don’t use it for click and contextmenu events, because the former happens only on left-click, and the latter – only on right-click.

From the other hand, mousedown and mouseup handlers may need event.button, because these events trigger on any button, so button allows to distinguish between “right-mousedown” and “left-mousedown”.

The possible values of event.button are:

Button state	event.button
Left button (primary)	0
Middle button (auxiliary)	1
Right button (secondary)	2
X1 button (back)	3
X2 button (forward)	4

Most mouse devices only have the left and right buttons, so possible values are 0 or 2. Touch devices also generate similar events when one taps on them.

Also there’s event.buttons property that has all currently pressed buttons as an integer, one bit per button. In practice this property is very rarely used, you can find details at MDN if you ever need it.

Old code may use event.which property that’s an old non-standard way of getting a button, with possible values:

• event.which 1 – left button,
• event.which 2 – middle button,
• event.which 3 – right button.

As of now, event.which is deprecated, we shouldn’t use it.

Modifiers: shift, alt, ctrl and meta

All mouse events include the information about pressed modifier keys.

Event properties:

• shiftKey: Shift
• altKey: Alt (or Opt for Mac)
• ctrlKey: Ctrl
• metaKey: Cmd for Mac

They are true if the corresponding key was pressed during the event.

For instance, the button below only works on Alt+Shift+click:

On Windows and Linux there are modifier keys Alt, Shift and Ctrl. On Mac there’s one more: Cmd, corresponding to the property metaKey.

In most applications, when Windows/Linux uses Ctrl, on Mac Cmd is used.

That is: where a Windows user presses Ctrl+Enter or Ctrl+A, a Mac user would press Cmd+Enter or Cmd+A, and so on.

So if we want to support combinations like Ctrl+click, then for Mac it makes sense to use Cmd+click. That’s more comfortable for Mac users.

Mouse Keys Left Click Windows 10

Even if we’d like to force Mac users to Ctrl+click – that’s kind of difficult. The problem is: a left-click with Ctrl is interpreted as a right-click on MacOS, and it generates the contextmenu event, not click like Windows/Linux.

So if we want users of all operating systems to feel comfortable, then together with ctrlKey we should check metaKey.

For JS-code it means that we should check if (event.ctrlKey || event.metaKey).

Keyboard combinations are good as an addition to the workflow. So that if the visitor uses a keyboard – they work.

But if their device doesn’t have it – then there should be a way to live without modifier keys.

Coordinates: clientX/Y, pageX/Y

All mouse events provide coordinates in two flavours:

1. Window-relative: clientX and clientY.
2. Document-relative: pageX and pageY.

We already covered the difference between them in the chapter Coordinates.

In short, document-relative coordinates pageX/Y are counted from the left-upper corner of the document, and do not change when the page is scrolled, while clientX/Y are counted from the current window left-upper corner. When the page is scrolled, they change.

For instance, if we have a window of the size 500x500, and the mouse is in the left-upper corner, then clientX and clientY are 0, no matter how the page is scrolled.

And if the mouse is in the center, then clientX and clientY are 250, no matter what place in the document it is. They are similar to position:fixed in that aspect.

Move the mouse over the input field to see clientX/clientY (the example is in the iframe, so coordinates are relative to that iframe):

Mouse button

Click-related events always have the button property, which allows to get the exact mouse button.

We usually don’t use it for click and contextmenu events, because the former happens only on left-click, and the latter – only on right-click.

From the other hand, mousedown and mouseup handlers may need event.button, because these events trigger on any button, so button allows to distinguish between “right-mousedown” and “left-mousedown”.

The possible values of event.button are:

Button state	event.button
Left button (primary)	0
Middle button (auxiliary)	1
Right button (secondary)	2
X1 button (back)	3
X2 button (forward)	4

Most mouse devices only have the left and right buttons, so possible values are 0 or 2. Touch devices also generate similar events when one taps on them.

Also there’s event.buttons property that has all currently pressed buttons as an integer, one bit per button. In practice this property is very rarely used, you can find details at MDN if you ever need it.

Old code may use event.which property that’s an old non-standard way of getting a button, with possible values:

• event.which 1 – left button,
• event.which 2 – middle button,
• event.which 3 – right button.

As of now, event.which is deprecated, we shouldn’t use it.

Modifiers: shift, alt, ctrl and meta

All mouse events include the information about pressed modifier keys.

Event properties:

• shiftKey: Shift
• altKey: Alt (or Opt for Mac)
• ctrlKey: Ctrl
• metaKey: Cmd for Mac

They are true if the corresponding key was pressed during the event.

For instance, the button below only works on Alt+Shift+click:

On Windows and Linux there are modifier keys Alt, Shift and Ctrl. On Mac there’s one more: Cmd, corresponding to the property metaKey.

In most applications, when Windows/Linux uses Ctrl, on Mac Cmd is used.

That is: where a Windows user presses Ctrl+Enter or Ctrl+A, a Mac user would press Cmd+Enter or Cmd+A, and so on.

So if we want to support combinations like Ctrl+click, then for Mac it makes sense to use Cmd+click. That’s more comfortable for Mac users.

Mouse Keys Left Click Windows 10

Even if we’d like to force Mac users to Ctrl+click – that’s kind of difficult. The problem is: a left-click with Ctrl is interpreted as a right-click on MacOS, and it generates the contextmenu event, not click like Windows/Linux.

So if we want users of all operating systems to feel comfortable, then together with ctrlKey we should check metaKey.

For JS-code it means that we should check if (event.ctrlKey || event.metaKey).

Keyboard combinations are good as an addition to the workflow. So that if the visitor uses a keyboard – they work.

But if their device doesn’t have it – then there should be a way to live without modifier keys.

Coordinates: clientX/Y, pageX/Y

All mouse events provide coordinates in two flavours:

1. Window-relative: clientX and clientY.
2. Document-relative: pageX and pageY.

We already covered the difference between them in the chapter Coordinates.

In short, document-relative coordinates pageX/Y are counted from the left-upper corner of the document, and do not change when the page is scrolled, while clientX/Y are counted from the current window left-upper corner. When the page is scrolled, they change.

For instance, if we have a window of the size 500x500, and the mouse is in the left-upper corner, then clientX and clientY are 0, no matter how the page is scrolled.

And if the mouse is in the center, then clientX and clientY are 250, no matter what place in the document it is. They are similar to position:fixed in that aspect.

Move the mouse over the input field to see clientX/clientY (the example is in the iframe, so coordinates are relative to that iframe):

Preventing selection on mousedown

Double mouse click has a side-effect that may be disturbing in some interfaces: it selects text.

For instance, double-clicking on the text below selects it in addition to our handler:

If one presses the left mouse button and, without releasing it, moves the mouse, that also makes the selection, often unwanted.

There are multiple ways to prevent the selection, that you can read in the chapter Selection and Range.

In this particular case the most reasonable way is to prevent the browser action on mousedown. It prevents both these selections:

Now the bold element is not selected on double clicks, and pressing the left button on it won’t start the selection.

Please note: the text inside it is still selectable. However, the selection should start not on the text itself, but before or after it. Usually that’s fine for users.

If we want to disable selection to protect our page content from copy-pasting, then we can use another event: oncopy.

If you try to copy a piece of text in the <div>, that won’t work, because the default action oncopy is prevented.

Surely the user has access to HTML-source of the page, and can take the content from there, but not everyone knows how to do it.

Summary

Mouse events have the following properties:

• Button: button.

• Modifier keys (true if pressed): altKey, ctrlKey, shiftKey and metaKey (Mac).

  • If you want to handle Ctrl, then don’t forget Mac users, they usually use Cmd, so it’s better to check if (e.metaKey || e.ctrlKey).

• Window-relative coordinates: clientX/clientY.

• Document-relative coordinates: pageX/pageY.

The default browser action of mousedown is text selection, if it’s not good for the interface, then it should be prevented.

In the next chapter we’ll see more details about events that follow pointer movement and how to track element changes under it.

Microsoft Windows users can change the properties of their mouse buttons by following the steps below.

Note

Some programs may use mouse settings that and overwrite the settings you specify in Windows. If, after following the steps below, your program is still not changing the mouse buttons, look for mouse settings in the program you want to change.

Change mouse buttons in Windows 8 and 10

1. On the Windows 8 Start screen or in the Windows 10 search field on the Taskbar, type mouse.
2. Select the change your mouse settings option in the search results.
3. In the Settings window, under Select your primary button, change the selected option in the drop-down list from Left to Right or Right to Left.

Set mouse buttons in Windows Vista and 7

1. Open the Control Panel.
2. Click Hardware and Sound
3. Click Mouse
4. In the Mouse Properties window, click the Buttons tab and click the Switch primary and secondary buttons check box.

Note

If you are missing the Buttons icon in the Mouse Properties window, reinstall the software included with your mouse or download and install the 'Microsoft mouse and keyboard center' software.

Keyboard Shortcut Left Mouse Click Change mouse buttons in Windows 2000 and XP

1. Open the Control Panel.
2. In the Control Panel, double-click the Mouse icon.
3. In the Mouse Properties window, click the Buttons tab and select the action for each of the buttons.

Change mouse buttons in Windows 95, 98, ME, and NT Mouse Keys Left Click Not Working

1. Open the Control Panel.
2. In the Control Panel, double-click the Mouse icon.
3. In the Mouse Properties window, click the Buttons tab and change the button configuration from right-handed to left-handed.

Additional information Left Click With Keyboard

• See the mouse and right-click definitions for further information and related links.