[wp-trac] [WordPress Trac] #45375: Support the richtext editing option in the block editor

[WordPress Trac]

#45375: Support the richtext editing option in the block editor
---------------------------------+------------------------------
 Reporter:  youknowriad          |       Owner:  danielbachhuber
     Type:  task (blessed)       |      Status:  reopened
 Priority:  normal               |   Milestone:  5.0
Component:  Editor               |     Version:  5.0
 Severity:  normal               |  Resolution:
 Keywords:  has-patch fixed-5.0  |     Focuses:
---------------------------------+------------------------------

Comment (by youknowriad):

 @zodiac1978

 > If I want to disable Gutenberg, I would install the Classic Editor
 plugin, that's what the callout is saying to the people. If I had checked
 the mentioned option I want to see markup instead of visual presentation.

 Agreed and that's what's happening with this patch.

 > Imagine someone with "Disable the visual editor when writing" checked
 and this person updates to WP 5.0 - will this person expect the block
 editor to be disabled, the block editor not usable, because there is no
 option to convert to blocks or will the person expect the editor to show
 HTML markup like before in the current editor (Classic or blocks)?

 I expect the Gutenberg editor to show the HTML markup in the current
 editor of WordPress which is Gutenberg in 5.0

 > Why do you think that people who had checked this option don't want to
 add blocks? I think this is the wrong assumption.

 That's a decision that has already been made in Gutenberg and that is
 independent from this patch. When you are in the Code editor of Gutenberg
 (regardless of the option in the user profile), you can't add blocks.

 --

 Did you try the patch? I think the patch is doing what you expect more or
 less. It's showing Gutenberg's code editor.

 This commit is not doing anything more than just back porting something
 from the Gutenberg editor which was already approved and merged. We can
 still iterate on that but it's better to open a GitHub issue for that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45375#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform