Changes lost when switching from code editor to visual editor

[jikamens]

1. Start composing a new post.
2. Enter some text in the visual editor.
3. Switch to the code editor with ctrl-alt-shift-m.
4. Make a change that should be visible in the visual editor, e.g., wrap <sup>...</sup> around some text to make it superscript.
5. Switch back to the visual editor with ctrl-alt-shift-m.
6. Observe that your change is not visible in the visual editor.
7. Click Save Draft.
8. Switch back to the code editor with ctrl-alt-shift-m.
9. Observe that your change is gone.

Ugh.

Marking this "major" severity because it's a data loss bug.

[sebastienserre]

Hello,

I reproduced but I'm not sure this a bug as if you save the draft just after making your change in the code editor, then you won't lost.

[jikamens]

1. "I'm not sure this is a bug because there's a completely undocumented workaround that no one could possibly know they need to do without first falling victim to the problem and losing data" is not a good take.

2. I've used a lot of rich text editors that allow switching between rich text and code, and none of the others behaves this way.

3. In fact, the old WordPress editor didn't behave this way, so this is a regression.

[noisysocks]

Reported here: ​https://github.com/WordPress/gutenberg/issues/22007

[jikamens]

This is fixed upstream, can we please make sure to get the fix into the next WordPress release?