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

minor fixes

Browse source
This commit is contained in:
Enrico Palmieri 2019-07-23 21:29:26 +02:00
parent 7c340a1be5
commit 9a4fe338fd
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
1-js/11-async/07-microtask-queue/article.md
View file

@ -10,12 +10,12 @@ Here's the demo:
```js run ```js run
let promise = Promise.resolve(); let promise = Promise.resolve();
promise.then(() => alert("promise done")); promise.then(() => alert("promise done!"));
alert("code finished"); // this alert shows first alert("code finished"); // this alert shows first
``` ```
If you run it, you see `code finished` first, and then `promise done`. If you run it, you see `code finished` first, and then `promise done!`.
That's strange, because the promise is definitely done from the beginning. That's strange, because the promise is definitely done from the beginning.
@ -54,7 +54,7 @@ Now the order is as intended.
## Unhandled rejection ## Unhandled rejection
Remember "unhandled rejection" event from the chapter <info:promise-error-handling>? Remember `unhandledrejection` event from the chapter <info:promise-error-handling>?
Now we can see exactly how JavaScript finds out that there was an unhandled rejection Now we can see exactly how JavaScript finds out that there was an unhandled rejection