jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

minor fixes

Browse source 
- fix erratas
- fix wrong error message
- add 'run' on runnable example
- add explanation about window.onload property corresponding load event
- add comment about window.onstorage property corresponding storage event
This commit is contained in:
Violet Bora Lee 2020-03-14 07:27:49 +09:00
parent 36737518f8
commit 958cbe72b8
8 changed files with 13 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/06-advanced-functions/03-closure/7-let-scope/solution.md
View file

@ -31,7 +31,7 @@ function func() {
// hence the error
*/!*
console.log(x); // ReferenceError: Cannot access 'vx before initialization
console.log(x); // ReferenceError: Cannot access 'x' before initialization
let x = 2;
}

2
1-js/06-advanced-functions/04-var/article.md
View file

@ -218,7 +218,7 @@ The Function Expression is wrapped with parenthesis `(function {...})`, because
```js run
// Try to declare and immediately call a function
function() { // <-- Error: Unexpected token (
function() { // <-- Error: Function statements require a function name
let message = "Hello";

2
1-js/99-js-misc/01-proxy/article.md
View file

@ -455,7 +455,7 @@ Such properties have their own issues though. In particular, they are not inheri
## "In range" with "has" trap
Let's see more examples.ar
Let's see more examples.
We have a range object:

2
2-ui/1-document/03-dom-navigation/article.md
View file

@ -201,7 +201,7 @@ The parent is available as `parentNode`.
For example:
```js
```js run
// parent of <body> is <html>
alert( document.body.parentNode === document.documentElement ); // true

2
2-ui/1-document/05-basic-dom-node-properties/article.md
View file

@ -36,7 +36,7 @@ It gets properties and methods as a superposition of (listed in inheritance orde
- `HTMLInputElement` -- this class provides input-specific properties,
- `HTMLElement` -- it provides common HTML element methods (and getters/setters),
- `Element` -- provides generic element methods,
- `Node` -- provides common DOM node properties,.
- `Node` -- provides common DOM node properties,
- `EventTarget` -- gives the support for events (to be covered),
- ...and finally it inherits from `Object`, so "plain object" methods like `hasOwnProperty` are also available.

8
2-ui/5-loading/01-onload-ondomcontentloaded/article.md
View file

@ -85,7 +85,7 @@ External style sheets don't affect DOM, so `DOMContentLoaded` does not wait for
But there's a pitfall. If we have a script after the style, then that script must wait until the stylesheet loads:
```html
```html run
<link type="text/css" rel="stylesheet" href="style.css">
<script>
// the script doesn't not execute until the stylesheet is loaded
@ -108,13 +108,13 @@ So if `DOMContentLoaded` is postponed by long-loading scripts, then autofill als
## window.onload [#window-onload]
The `load` event on the `window` object triggers when the whole page is loaded including styles, images and other resources.
The `load` event on the `window` object triggers when the whole page is loaded including styles, images and other resources. This event is available via the `onload` property.
The example below correctly shows image sizes, because `window.onload` waits for all images:
```html run height=200 refresh
<script>
window.onload = function() {
window.onload = function() { // same as window.addEventListener('load', (event) => {
alert('Page loaded');
// image is loaded at this time
@ -277,7 +277,7 @@ Page load events:
- Images and other resources may also still continue loading.
- The `load` event on `window` triggers when the page and all resources are loaded. We rarely use it, because there's usually no need to wait for so long.
- The `beforeunload` event on `window` triggers when the user wants to leave the page. If we cancel the event, browser asks whether the user really wants to leave (e.g we have unsaved changes).
- `The unload` event on `window` triggers when the user is finally leaving, in the handler we can only do simple things that do not involve delays or asking a user. Because of that limitation, it's rarely used. We can send out a network request with `navigator.sendBeacon`.
- The `unload` event on `window` triggers when the user is finally leaving, in the handler we can only do simple things that do not involve delays or asking a user. Because of that limitation, it's rarely used. We can send out a network request with `navigator.sendBeacon`.
- `document.readyState` is the current state of the document, changes can be tracked in the `readystatechange` event:
- `loading` -- the document is loading.
- `interactive` -- the document is parsed, happens at about the same time as `DOMContentLoaded`, but before it.

2
6-data-storage/02-localstorage/article.md
View file

@ -202,7 +202,7 @@ If both windows are listening for `window.onstorage`, then each one will react o
```js run
// triggers on updates made to the same storage from other documents
window.onstorage = event => {
window.onstorage = event => { // same as window.addEventListener('storage', () => {
if (event.key != 'now') return;
alert(event.key + ':' + event.newValue + " at " + event.url);
};