jesseskinner/dompatch

Patch the DOM in the most efficient way possible.

dompatch's Issues

Deal with attributes (eg. type, name) that the browser refuses to change.

You usually can't change the type of an input, so I'll need to test that and maybe have a special condition on input elements.

Apparently older Internet Explorer won't allow the name attribute to change either so will need to test that.

Perhaps a generic solution would be to catch errors in updating attributes or child nodes, and simply revert to replacing the element in that case. That'd probably make it future-proof in case HTML6+ introduces any read-only attributes or other such restrictions.

Garbage collection can be brutally slow

If we're generating and abandoning a large number of documents and nodes in a short time, garbage collection can be a major performance bottleneck.

Technically, this problem is out of the scope of this project, as dompatch only compares two documents/elements and updates them accordingly. But in practical terms, it'd be great to have an example that gets around this bottleneck, and the solution may likely need changes made to dompatch to allow this workaround.

Alternatively, this may be an acceptable limitation of dompatch's overall approach. If so, we may need to add a warning about it, that dompatch can be janky in some circumstances.