-
-
Notifications
You must be signed in to change notification settings - Fork 330
Investigate MorphDOM vs ReactDOM #883
Copy link
Copy link
Open
Labels
priority-3-lowMay be resolved one any timeline.May be resolved one any timeline.type-investigationAbout research and gathering informationAbout research and gathering information
Description
Activity
Metadata
Metadata
Assignees
Labels
priority-3-lowMay be resolved one any timeline.May be resolved one any timeline.type-investigationAbout research and gathering informationAbout research and gathering information
Currently, due to the addition of our
reactpy.html.scripttag, there is now the potential of user's manually manipulating the client side DOM, which will cause a mismatch when comparing to the server side VDOM. This can cause client side exceptions within ReactDOM when the attempting to change/modify/add/delete nodes or attributes that no longer exist. We may want to consider switching to MorphDOM to account for this, since it could automatically mutate the client DOM to meet the server side VDOM model.This issue exists to debate whether MorphDOM should be considered as an alternative, or whether we should simply work around these issues with React-DOM.
Note: Originally discussed in #798 by Archmonger August 10, 2022