You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building a rich text editor solution based on the block editor can lead to unexpected interactions. On deselection of a block, we lose the toolbar and UI for the text editor.
This would be useful so that WooCommerce can use the block based editor for its new rich text editor solution.
Before deselection:
After deselection
What is your proposed solution?
If we can prevent clearing of items in some way, that would be ideal. This could either be through a prop or simply handling the deselection on click instead of mousedown so we can revert deselection in the consuming component.
Help us move this issue forward. This issue is being marked stale since it has no activity after 15 days of requesting more information. Please add info requested so we can help move the issue forward. Note: The triage policy is to close stale issues that need more info and no response after 2 weeks.
What problem does this address?
Building a rich text editor solution based on the block editor can lead to unexpected interactions. On deselection of a block, we lose the toolbar and UI for the text editor.
This would be useful so that WooCommerce can use the block based editor for its new rich text editor solution.
Before deselection:
After deselection
What is your proposed solution?
If we can prevent clearing of items in some way, that would be ideal. This could either be through a prop or simply handling the deselection on
click
instead ofmousedown
so we can revert deselection in the consuming component.gutenberg/packages/block-editor/src/components/block-selection-clearer/index.js
Lines 19 to 47 in 8aa2aa2
The text was updated successfully, but these errors were encountered: