[wp-trac] [WordPress Trac] #45375: Support the richtext editing option in the block editor
WordPress Trac
noreply at wordpress.org
Wed Nov 21 14:05:23 UTC 2018
#45375: Support the richtext editing option in the block editor
----------------------------+-----------------------
Reporter: youknowriad | Owner: (none)
Type: task (blessed) | Status: reopened
Priority: normal | Milestone: 5.0
Component: Editor | Version: 5.0
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
----------------------------+-----------------------
Comment (by zodiac1978):
> That's what the option is for
No, it was an option for a complete different case. We are just guessing
what's the best way to move on here.
> it's not about on boarding into Gutenberg.
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)?
> People that want the code editor, don't want to add blocks and then edit
them as HTML.
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.
Why do you think that people who had checked this option don't want to add
blocks? I think this is the wrong assumption.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45375#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list