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:
Ilya Kantor 2020-09-13 23:56:48 +03:00
parent bd8e8a9bdd
commit c1e7bcb0df
1 changed files with 9 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

13
2-ui/99-ui-misc/01-mutation-observer/article.md
View file

@ -243,14 +243,19 @@ When we stop the observing, it might be possible that some changes were not yet
These methods can be used together, like this: These methods can be used together, like this:
```js ```js
// we'd like to stop tracking changes // get a list of unprocessed mutations
observer.disconnect();
// handle unprocessed some mutations
let mutationRecords = observer.takeRecords(); let mutationRecords = observer.takeRecords();
// stop tracking changes
observer.disconnect();
... ...
``` ```
```smart header="Records returned by `observer.takeRecords()` are removed from the processing queue"
The callback won't be called for records, returned by `observer.takeRecords()`.
```
```smart header="Garbage collection interaction" ```smart header="Garbage collection interaction"
Observers use weak references to nodes internally. That is, if a node is removed from the DOM, and becomes unreachable, then it can be garbage collected. Observers use weak references to nodes internally. That is, if a node is removed from the DOM, and becomes unreachable, then it can be garbage collected.