What problem does this address?
When a user switches from Visual Editor to Code Editor during a real-time collaboration session, changes appear to sync correctly in the Code Editor view. However, when switching back to Visual Editor, the old (pre-sync) values are displayed instead of the updated content.
I have also seen behavior where making changes in the Code Editor can cause content to be lost in the visual editor.
What is your proposed solution?
Determine what it would take to make the Code Editor work in a collaborative environment, ideally, collaborators can switch back and forth with no noticeable difference.
This will likely require delaying changes made in the Code Editor that may result in parsing errors so that these ephemeral errors don't appear for other collaborators.
These issues may prove difficult to resolve, and an interim solution that disables code editing during a collaborative session may be required.
What problem does this address?
When a user switches from Visual Editor to Code Editor during a real-time collaboration session, changes appear to sync correctly in the Code Editor view. However, when switching back to Visual Editor, the old (pre-sync) values are displayed instead of the updated content.
I have also seen behavior where making changes in the Code Editor can cause content to be lost in the visual editor.
What is your proposed solution?
Determine what it would take to make the Code Editor work in a collaborative environment, ideally, collaborators can switch back and forth with no noticeable difference.
This will likely require delaying changes made in the Code Editor that may result in parsing errors so that these ephemeral errors don't appear for other collaborators.
These issues may prove difficult to resolve, and an interim solution that disables code editing during a collaborative session may be required.