You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having an issue with quill editors nested inside of quill blots (imagine an image blot with a title field that is a quill richtext editor). In Parchment’s scroll.ts, the MutationObserver for the parent editor hears any mutation in the nested field, and applies the change to itself. This leads to behavior where text typed in the nested field is applied to both the nested editor and the parent editor. I believe this behavior can be fixed by checking the target node of the MutationRecord, looking up the parent tree for the closest .ql-editor, and only applying the update to the quill instance with that DOM node. I am using quill version 1.3.3
The text was updated successfully, but these errors were encountered:
I am having an issue with quill editors nested inside of quill blots (imagine an image blot with a title field that is a quill richtext editor). In Parchment’s scroll.ts, the MutationObserver for the parent editor hears any mutation in the nested field, and applies the change to itself. This leads to behavior where text typed in the nested field is applied to both the nested editor and the parent editor. I believe this behavior can be fixed by checking the target node of the MutationRecord, looking up the parent tree for the closest .ql-editor, and only applying the update to the quill instance with that DOM node. I am using quill version 1.3.3
The text was updated successfully, but these errors were encountered: