Classic Block: Restore HTML editing option#73865
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @GovardhaneNitin, @jfacemyer, @DavidBorrink. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
t-hamano
left a comment
There was a problem hiding this comment.
LGTM!
I never imagined anyone would use HTML editing in the Classic block 😅 This approach seems fine for now.
|
Everyone is using WP in different ways, there's no need to break their environments if we can avoid it :) |
|
Hey, thank you all. We look forward to the rollout, er "rollback" when that gets released. |
Unlinked contributors: GovardhaneNitin, jfacemyer, DavidBorrink. Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
Unlinked contributors: GovardhaneNitin, jfacemyer, DavidBorrink. Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
|
This PR has been backported to the |
What?
Closes #73792.
Re-opens #10837.
PR restores HTML editing functionality for the Classic block, based on the feedback from #73792.
Let's try to solve the original problem using
autopand Classic: #10837 (comment).Testing Instructions
Testing Instructions for Keyboard
Same.