3 ms·
The missing part in the DOM is: freeze() doLotsOfUpdates() thaw() So one would have to reinvent this. Kind of reminds of propeties in some languages,
by malkia 11y ago
The missing part in the DOM is:
freeze()
doLotsOfUpdates()
thaw()
So one would have to reinvent this. Kind of reminds of propeties in some languages, runtimes and their UI's:
someForm.setWidth(500); // And it's updated right away on the screen, instead of being deferred, or put in some freeze()/thaw() mode. (disableUpdates() / enabledUpdates()).
- WalterGR 11y agoIs there any ongoing effort to add 'freeze' and 'thaw' to the standard? Or any browsers that have added them?
- Yaggo 11y agoIsn't requestAnimationFrame basically that?
- avodonosov 11y agoOur scripts are executed in a freeze mode. When we modify DOM it becomes "dirty", and after our script finishes, reflow/re-render happens. But also, if our script queries DOM properties, like elem.clientHeight, DOM may need to perform the calculations in order to return us correct values, reflecting all the recent property changes. For example, if we access element.clientHeight browser may need to calculate re-flow (I recently encountered very slow clientHeight calculation by FireFox). So, if we only modify DOM properties, all the re-rendering is deferred till the end of script. Google about "DOM reflow"