AFAIK, innerHTML causes copies / creation of transient DocumentFragments and shouldn't be used in loops / event callbacks for long-lived process and/or frequently changed UI elements. This instead reuses existing child and updates it in-place.
In any case it should be at least be an improvement to perf.
cc @cosmicdreams (who had mentioned some issues with the application crashing: this might be a cause?)
AFAIK, innerHTML causes copies / creation of transient
DocumentFragments and shouldn't be used in loops / event callbacks for long-lived process and/or frequently changed UI elements. This instead reuses existing child and updates it in-place.In any case it should be at least be an improvement to perf.
cc @cosmicdreams (who had mentioned some issues with the application crashing: this might be a cause?)