Ввод пользователя и управление
==============================

 Это руководство содержит рекомендации по обработке пользовательского ввода
 и внедрению управляющих элементов в веб-приложения. Также здесь вы найдёте соответствующие FAQs, живые примеры, ссылки на более подробные разборы близлежащих технологий.
 Связанные интерфейсы API и события: события касаний, интерфейс отслеживания указателя мыши,
 интерфейс ориентации экрана,
 интерфейс режима "на весь экран" (en-US), перетаскивание и сброс и т. д.

Рабочая область
---------------

The following diagram illustrates the typical workflow for implementing user input mechanisms:

![](/ru/docs/Learn/Forms/User_input_methods/user-input-and-controls.png)

First of all, you need to decide which input mechanisms you want to cover in your application out of mouse, keyboard, finger touch and so on. Once you decided the input mechanisms, you can control them using tools offered by the web platform or JavaScript libraries.

Recommendations
---------------

Available input mechanisms depend on the capabilities of the device running the application:

* Some devices provide touchscreen displays: the Web Platform offers touch events (en-US) to interpret finger activity on touch-based user interfaces.
* For devices providing a mouse/touchpad as a pointing method, the Pointer Lock API helps you in implementing a first person 3D game or other applications requiring full control of the pointing device. And the Fullscreen API (en-US) helps you in displaying your app in fullscreen mode.
* Using features such as contentEditable (en-US) elements you can implement fast rich-text editors and with Drag&Drop let users moving elements inside your app. When screen orientation matters for your application, through the Screen Orientation API you can read the screen orientation state and perform other actions.
* You should always be mindful of keyboard accessibility where appropriate — many web users only use keyboard to navigate web sites and apps, and locking them out of your functionality is a bad idea.

The following is a set of recommendations and best practices for using such tools in Open Web Apps.

### Decide what input mechanism you're using

#### Keyboard

Keyboard input can be controlled by your app. For example if you want to add controls when any key gets pressed, you need to add an event listener on the window object:


```js
window.addEventListener("keydown", handleKeyDown, true);
window.addEventListener("keyup", handleKeyUp, true);
```


where `handleKeyDown` and `handleKeyUp` are the functions implementing the controls about the `keydown` and `keyup` events.

**Примечание:** Have a look at the Events reference (en-US) and `KeyboardEvent` guide to find out more about keyboard events.

#### Mouse

The events occurring when the user interacts with a pointing device such as a mouse are represented by the `MouseEvent` DOM Interface. Common mouse events include `click` (en-US), `dblclick` (en-US), `mouseup` (en-US), and `mousedown` (en-US). The list of all events using the Mouse Event Interface is provided in the Events reference (en-US).

When the input device is a mouse, you can also control user input through the Pointer Lock API and implement Drag & Drop (see below).

#### Finger touch

When developing web applications meant to be installed on touchscreen devices, it's a good practice to take into consideration the different capabilities in terms of screen resolution and user input. Touch events (en-US) can help you implement interactive elements and common interaction gestures on touchscreen devices.

If you want to use touch events, you need to add event listeners and specify handler functions, which will be called when the event gets fired:


```js
element.addEventListener("touchstart", handleStart, false);
element.addEventListener("touchcancel", handleCancel, false);
element.addEventListener("touchend", handleEnd, false);
element.addEventListener("touchmove", handleMove, false);
```


where `element` is the DOM element you want to register the touch events on.

**Примечание:** For further information about what you can do with touch events, please read our touch events guide (en-US).

#### Pointer Events

When dealing with devices that incorporate multiple forms of input, like mouse, finger touch and pen input, it might be hard to develop a solution that works for all these different control mechanisms. Pointer Events help developers more easily manage events across devices by normalizing the handling of each one. A pointer can be any point of contact on the screen made by a mouse cursor, pen, touch (including multi-touch), or other pointing input device. The events for handling generic pointer input look a lot like those for mouse: `pointerdown`, `pointermove`, `pointerup`, `pointerover`, `pointerout`, etc.

**Примечание:** Pointer Events are not widely supported yet, but a pointer.js polyfill is available on Mozilla Github.

### Implement controls

#### Pointer lock

In some cases, typically game development, you might need to access mouse events even when the cursor goes past the boundary of the browser or screen: the `Pointer_Lock_API` gives you full control of the pointing device.

This is the code to request pointer lock on an `element`:


```js
element.requestPointerLock();
```


**Примечание:** For a full tutorial and reference, read our `Pointer_Lock_API` page.

#### Screen Orientation

When screen orientation matters for your application, you can read the screen orientation state, be informed when this state changes, and able to lock the screen orientation to a specific state (usually portrait or landscape) through the Screen Orientation API.

Orientation data can be retrieved through the `screen.orientation` (en-US) attribute or through the `orientation` (en-US) media feature. When `screen.orientation` changes, the `screen.orientationchange` event is fired on the screen object. Locking the screen orientation is made possible by invoking the `screen.lockOrientation` (en-US) method, while the `screen.unlockOrientation` (en-US) method removes all the previous screen locks that have been set.

**Примечание:** More information about the Screen Orientation API can be found in Managing screen orientation.

#### Fullscreen

You might need to present an element of your application (such as a `<video>`, for example) in fullscreen mode. You can achieve this by calling `Element.requestFullscreen()` (en-US) on that element. Bear in mind that many browsers still implement this with a vendor prefix, so you will probably need to fork your code something like this:


```js
var elem = document.getElementById("myvideo");
if (elem.requestFullscreen) {
  elem.requestFullscreen();
} else if (elem.msRequestFullscreen) {
  elem.msRequestFullscreen();
} else if (elem.mozRequestFullScreen) {
  elem.mozRequestFullScreen();
} else if (elem.webkitRequestFullscreen) {
  elem.webkitRequestFullscreen();
}
```


**Примечание:** To find more out about adding fullscreen functionality your application, read our documentation about using fullscreen mode (en-US).

#### Drag & Drop

Drag & Drop allows your application's users to click and hold the mouse button down over an element, drag it to another location, and release the mouse button to drop the element there.

Here is an example that allows a section of content to be dragged.


```html
<div
 draggable="true"
 ondragstart="event.dataTransfer.setData('text/plain', 'This text may be dragged')">
  This text <strong>may</strong> be dragged.
</div>
```


in which we:

* Set the `draggable` attribute to true on the element that you wish to make draggable
* Add a listener for the `dragstart` (en-US) event and set the drag data within this listener

**Примечание:** You can find more information in the MDN Drag & Drop documentation.

#### contentEditable

In open web apps any DOM element can be made directly editable using the `contenteditable` attribute.


```html
<div contenteditable="true">This text can be edited by the user.</div>
```


**Примечание:** Compatibility information, examples and other resources can be found in the Content Editable guide (en-US).

Examples
--------

**Tracking multiple touch points at a time**

This example tracks multiple touch points at a time, allowing the user to draw in a ``<canvas>`` with more than one finger at a time. It will only work on a browser that supports touch events.

**Simple pointer lock demo**

We've written a simple pointer lock demo to show you how to use it to set up a simple control system. The demo uses JavaScript to draw a ball inside a ``<canvas>`` element. When you click the canvas, pointer lock is then used to remove the mouse pointer and allow you to move the ball directly using the mouse.

**contentEditable demo**

This is a working example showing how contenteditable can be used to create an editable document section, the state of which is then saved using LocalStorage (en-US).

Руководства
-----------

* События касаний (тач-события) - руководство
* Разбираемся с ориентацией экрана
* Использование полноэкранного режима (en-US)
* Перетаскивание и сброс нескольких объектов
* Руководство по перетаскиванием
Смотрите также
--------------

* `MouseEvent`
* `KeyboardEvent`
* Touch events (en-US)
* `Pointer_Lock_API`
* Screen Orientation API
* Fullscreen API (en-US)
* Drag & Drop
* Content Editable (en-US)
* Keyboard events in Firefox OS TV
* Implementing TV remote control navigation