You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. We load `3.js`, then if there's no error -- do something else `(*)`.
235
235
236
236
As calls become more nested, the code becomes deeper and increasingly more difficult to manage, especially if we have real code instead of `...` that may include more loops, conditional statements and so on.
@@ -299,7 +299,7 @@ function step3(error, script) {
299
299
}
300
300
```
301
301
302
-
See? It does the same, and there's no deep nesting now because we made every action a separate top-level function.
302
+
See? It does the same thing, and there's no deep nesting now because we made every action a separate top-level function.
303
303
304
304
It works, but the code looks like a torn apart spreadsheet. It's difficult to read, and you probably noticed that one needs to eye-jump between pieces while reading it. That's inconvenient, especially if the reader is not familiar with the code and doesn't know where to eye-jump.
Copy file name to clipboardExpand all lines: 2-ui/2-events/04-default-browser-action/article.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ There are two ways to tell the browser we don't want it to act:
17
17
- The main way is to use the `event` object. There's a method `event.preventDefault()`.
18
18
- If the handler is assigned using `on<event>` (not by `addEventListener`), then returning `false` also works the same.
19
19
20
-
In this HTML a click on a link doesn't lead to navigation, browser doesn't do anything:
20
+
In this HTML, a click on a link doesn't lead to navigation; the browser doesn't do anything:
21
21
22
22
```html autorun height=60 no-beautify
23
23
<ahref="/"onclick="return false">Click here</a>
@@ -96,7 +96,7 @@ That's because the browser action is canceled on `mousedown`. The focusing is st
96
96
97
97
The optional `passive: true` option of `addEventListener` signals the browser that the handler is not going to call `preventDefault()`.
98
98
99
-
Why that may be needed?
99
+
Why might that be needed?
100
100
101
101
There are some events like `touchmove` on mobile devices (when the user moves their finger across the screen), that cause scrolling by default, but that scrolling can be prevented using `preventDefault()` in the handler.
Copy file name to clipboardExpand all lines: 2-ui/3-event-details/1-mouse-events-basics/article.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,9 +39,9 @@ In cases when a single action initiates multiple events, their order is fixed. T
39
39
```online
40
40
Click the button below and you'll see the events. Try double-click too.
41
41
42
-
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.
42
+
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 rule.
43
43
44
-
Also we can see the `button` property that allows to detect the mouse button, it's explained below.
44
+
Also, we can see the `button` property that allows us to detect the mouse button; it's explained below.
45
45
46
46
<input onmousedown="return logMouse(event)" onmouseup="return logMouse(event)" onclick="return logMouse(event)" oncontextmenu="return logMouse(event)" ondblclick="return logMouse(event)" value="Click me with the right or the left mouse button" type="button"> <input onclick="logClear('test')" value="Clear" type="button"> <form id="testform" name="testform"> <textarea style="font-size:12px;height:150px;width:360px;"></textarea></form>
0 commit comments