The classic editor block does not respect the user nor post setting about using Visual or HTML editors

[decodekult]

Describe the bug
When a post is created or edited, the editor being used upon save is kept as default. In addition, users have a setting in their profile about using by default the Visual or HTML editor.

However, when enabling Gutenberg all posts cntent is transformed into a classic editor block, which defaults to the Visual editor mode. It has the potential to break and corrupt existing content, since the Visual tab does not support HTML inside shortcodes content as the HTML editor does, as described here: #12068 (comment)

To Reproduce
Steps to reproduce the behavior:

1. Create a post with the latest stable WordPress release, switch to the HTML editor tab, and publish the post.
2. The post editor will be offering the HTML editor tab onwards.
3. Install the beta or the Gutenberg plugin and open the post to edit.
4. The post content will be editabe in the classic editor block Visual mode.

Expected behavior
The classic editor block should respect the user setting about disabling the Visual editor, or at least the user last edited mode for this given post.

Desktop (please complete the following information):

• OS: Wndows 10 64
• Browser firefox
• Version 63

Additional context

• Gutenberg plugin 4.4.0
• WordPress 5.1-alpha-43678

[designsimply]

@decodekult did you mean to close this issue?

[decodekult]

Yes, mainly for two reasons:

• My main concer was data loss. I assumed that content formatted with the HTML editor, once saved with the Visual mode of the classic editor block, could get corrupted. I noticed this is nto the case.
• The same, but extended and better explained, request has been just merged at Honor the Disable Visual Editor setting #12000