up
This commit is contained in:
parent
e4db23fa56
commit
4ae129054e
8 changed files with 3 additions and 3 deletions
|
@ -96,7 +96,7 @@ There are only 5 of them in JavaScript:
|
||||||
: With this flag the search looks for all matches, without it -- only the first one (we'll see uses in the next chapter).
|
: With this flag the search looks for all matches, without it -- only the first one (we'll see uses in the next chapter).
|
||||||
|
|
||||||
`m`
|
`m`
|
||||||
: Multiline mode (will cover in [todo]).
|
: Multiline mode (covered in the chapter <info:regexp-multiline>).
|
||||||
|
|
||||||
`u`
|
`u`
|
||||||
: Enables full unicode support. The flag enables correct processing of surrogate pairs. More about that in the chapter <info:regexp-unicode>.
|
: Enables full unicode support. The flag enables correct processing of surrogate pairs. More about that in the chapter <info:regexp-unicode>.
|
||||||
|
|
|
@ -4,7 +4,7 @@ Let's study keyboard events.
|
||||||
|
|
||||||
Before we start, please note that on modern devices there are other ways to "input something" then just a keyboard. For instance, people use speech recognition (tap microphone, say something, see it entered) or copy/paste with a mouse.
|
Before we start, please note that on modern devices there are other ways to "input something" then just a keyboard. For instance, people use speech recognition (tap microphone, say something, see it entered) or copy/paste with a mouse.
|
||||||
|
|
||||||
So if we want to track any input into an `<input>` field, then keyboard events is not enough. There's another event named `input` to handle changes of an `<input>` field, by any means. And it may be a better choice for such task. We'll cover it a bit later [todo link].
|
So if we want to track any input into an `<input>` field, then keyboard events is not enough. There's another event named `input` to handle changes of an `<input>` field, by any means. And it may be a better choice for such task. We'll cover it later in the chapter <info:events-change-input>.
|
||||||
|
|
||||||
Keyboard events should be used when we want to handle keyboard actions (virtual keyboard usually also counts). For instance, to react on arrow keys `key:Up` and `key:Down` or hotkeys (including combinations of keys).
|
Keyboard events should be used when we want to handle keyboard actions (virtual keyboard usually also counts). For instance, to react on arrow keys `key:Up` and `key:Down` or hotkeys (including combinations of keys).
|
||||||
|
|
||||||
|
|
|
@ -137,7 +137,7 @@ For windows with URLs from another sites, we are able to change the location by
|
||||||
|
|
||||||
A popup may access the "opener" window as well. A JavaScript in it may use `window.opener` to access the window that opened it. It is `null` for all windows except popups.
|
A popup may access the "opener" window as well. A JavaScript in it may use `window.opener` to access the window that opened it. It is `null` for all windows except popups.
|
||||||
|
|
||||||
So both the main window and the popup have a reference to each other. Thay may modify each other freely assuming that they come from the same origin. If that's not so, then there are still means to communicate, to be covered later [todo when].
|
So both the main window and the popup have a reference to each other. Thay may modify each other freely assuming that they come from the same origin. If that's not so, then there are still means to communicate, to be covered in the next chapter <info:cross-window-communication>.
|
||||||
|
|
||||||
## Closing a popup
|
## Closing a popup
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue